Skip to content

[BUG] logicAppsAccessControlConfiguration missing on Microsoft.Web/sites for Logic App Standard #32654

Open
@remyblok

Description

@remyblok

API Spec link

https://github.com/Azure/azure-rest-api-specs/blob/main/specification/web/resource-manager/Microsoft.Web/stable/2024-04-01/WebApps.json

API Spec version

2024-04-01

Describe the bug

As described by arjunchiddarwar in 'Trigger workflows in Standard logic apps with Easy Auth', Logic App Standard can be configured not to accept SAS tokens for HTTP triggers using the following ARM.

"logicAppsAccessControlConfiguration": {
    "triggers": {
        "sasAuthenticationPolicy": {
            "State": "Disabled"
        }
    }
}

Expected behavior

logicAppsAccessControlConfiguration is available as property on Microsoft.Web/sites

Actual behavior

logicAppsAccessControlConfiguration is not a known property on Microsoft.Web/sites. When deploying ARM/Bicep using the property the deployment succeeds and looking in the Azure Resource Explorer the property is set correctly.

Reproduction Steps

Used Bicep that works, but the logicAppsAccessControlConfigurationis not recognized as valid property. I have valided that this is not a Bicep issue, but that the property is also missing in this repo.

resource functionApp 'Microsoft.Web/sites@2024-04-01' = {
	name: functionAppName
	location: location
	kind: 'functionapp,workflowapp'
	properties: {
                ...,
		logicAppsAccessControlConfiguration: {
			triggers: {
				sasAuthenticationPolicy: {
					state: 'Disabled'
				}
			}
		}
	}
}

Environment

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    MgmtThis issue is related to a management-plane library.Service AttentionWorkflow: This issue is responsible by Azure service team.Web AppsbugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions