Error in creating Static Web App with location restriction policy

Question

Error in creating Static Web App with location restriction policy

Sivaprasad Chidambaram 20

I am getting the below error while creating Static Web App with the location restriction policy. There was no api location provided. How to overcome this?

{"code":"RequestDisallowedByPolicy","target":"StaticWebApp","message":"Resource 'StaticWebApp' was disallowed by policy. Policy identifiers: '[{\"policyAssignment\":{\"name\":\"Allowed locations for resource groups\",\"id\":\"/subscriptions/b7ceb4b5-7aa6-4b70-a468-16c31d16e5fb/providers/Microsoft.Authorization/policyAssignments/2360596671a4403baa122ed4\"},\"policyDefinition\":{\"name\":\"Allowed locations for resource groups\",\"id\":\"/providers/Microsoft.Authorization/policyDefinitions/e765b5de-1225-4ba3-bd56-1ac6695af988\",\"version\":\"1.0.0\"}}]'.","additionalInfo":[{"type":"PolicyViolation","info":{"evaluationDetails":{"evaluatedExpressions":[{"result":"True","expressionKind":"Field","expression":"type","path":"type","expressionValue":"Microsoft.Resources/subscriptions/resourceGroups","targetValue":"Microsoft.Resources/subscriptions/resourceGroups","operator":"Equals"},{"result":"True","expressionKind":"Field","expression":"location","path":"location","expressionValue":"centralus","targetValue":["centralindia","southindia","westindia","eastus","global"],"operator":"NotIn"}]},"policyDefinitionId":"/providers/Microsoft.Authorization/policyDefinitions/e765b5de-1225-4ba3-bd56-1ac6695af988","policyDefinitionName":"e765b5de-1225-4ba3-bd56-1ac6695af988","policyDefinitionDisplayName":"Allowed locations for resource groups","policyDefinitionVersion":"1.0.0","policyDefinitionEffect":"deny","policyAssignmentId":"/subscriptions/b7ceb4b5-7aa6-4b70-a468-16c31d16e5fb/providers/Microsoft.Authorization/policyAssignments/2360596671a4403baa122ed4","policyAssignmentName":"2360596671a4403baa122ed4","policyAssignmentDisplayName":"Allowed locations for resource groups","policyAssignmentScope":"/subscriptions/b7ceb4b5-7aa6-4b70-a468-16c31d16e5fb","policyAssignmentParameters":{"listOfAllowedLocations":["centralindia","southindia","westindia","eastus","global"]},"policyExemptionIds":[],"policyEnrollmentIds":[]}}]}

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Bhargavi Naragani 7,935 Microsoft External Staff Moderator

Hi @Sivaprasad Chidambaram,

From the error message you've encountered while trying to create an Azure Static Web App, it appears that the deployment is being blocked by an Azure Policy that restricts where resources can be created. Specifically, the policy named "Allowed locations for resource groups" is denying the request because the region you’re trying to use (centralus) is not on the allowed list for your subscription. Your organization has defined a policy to enforce resource creation only in certain regions, likely for compliance, data residency, or governance reasons.

According to the error allowed regions are: centralindia, southindia, westindia, eastus, and global and your attempted region: centralus – which is not allowed. As a result, Azure is blocking the creation of the resource, in this case, the Static Web App.

To resolve the issue:

Update your deployment to use one of the allowed locations mentioned in the policy:

centralindia
southindia
westindia
eastus
global (for globally distributed services like Azure CDN or DNS)

When creating the Static Web App, make sure you specify the location as one of the above in your deployment template or CLI command.

If you have a valid reason to deploy the resource in a different location (e.g., centralus), you can reach out to your Azure subscription or policy administrator. Request a policy exemption or an update to the policy to include centralus as an allowed region. This is typically done by someone with Owner or Policy Contributor permissions at the subscription level.

Kindly refer to the below documentation for better understanding:
Azure Policy: Deny resource creation based on location
Azure Static Web Apps – Overview and region availability
Manage policy assignments in Azure

If the answer is helpful, please click Accept Answer and kindly upvote it so that other people who faces similar issue may get benefitted from it.

Let me know if you have any further Queries.

Sivaprasad Chidambaram 20 Reputation points

2025-05-13T08:44:43.5333333+00:00

The API selection has only the regions as in the attached screenshot.

Why this has to be selected when my app has no APIs defined and it is just a static web app?

Any way this can be circumvented.
Bhargavi Naragani 7,935 Reputation points Microsoft External Staff Moderator

2025-05-13T09:23:24.2866667+00:00
Hi @Sivaprasad Chidambaram,

Even if your Static Web App doesn't include any custom Azure Functions (APIs) right now, Azure still requires a region to be specified for the "Functions and staging environments" section during creation. This is because Azure provisions infrastructure for potential staging slots, preview environments, or if you decide to add APIs in the future. Unfortunately, Azure doesn’t allow skipping this field, even for pure front-end apps without backends. This is by design and is not currently bypassable.

From your screenshot, Azure is only showing API regions like Central US, East US 2, etc. However, based on the policy set on your subscription, you’re only allowed to deploy resources in the regions centralindia, southindia, westindia, eastus, global this means the dropdown options currently available do not comply with your policy, hence you're blocked from creating the app.

You can use Azure CLI to explicitly set the location for the Static Web App to one of the allowed regions, such as eastus, like this:

az staticwebapp create \ --name my-static-app \ --resource-group my-resource-group \ --location eastus \ --source https://github.com/<user>/<repo> \ --branch main \ --app-location "/" \ --output-location "build"

You can omit the --api-location if you don’t have APIs, Azure will still create the underlying infrastructure but won’t provision Azure Functions unless specified. Azure CLI: Create Static Web Apps

If CLI option doesn't solve it, if you're still blocked, it's possible that the portal or backend validation still checks for a default API region, even if no API is defined. In this case, please reach out to your Azure admin or policy manager to either temporarily exempt your subscription from the “Allowed locations” policy or add a missing region (like East US 2 or Central US) to the allowed list.
Sivaprasad Chidambaram 20 Reputation points

2025-05-13T09:39:54.41+00:00

Thanks @Bhargavi Naragani .. Will try out and get back.
Bhargavi Naragani 7,935 Reputation points Microsoft External Staff Moderator

2025-05-13T11:04:29.0466667+00:00

Hi Sivaprasad Chidambaram,
If this answers your query and pointed you in the right direction, do click Accept Answer and Yes, if you have any further query do let us know.
Sivaprasad Chidambaram 20 Reputation points

2025-05-13T12:12:32.5966667+00:00

@Bhargavi Naragani It works only when the allowed region in the policy matches with the regions available in the static web app creation process. In my case I had eastus in the allowed region and selecting useast2 in the static web app only worked. For all others, the API throws the same error.
Bhargavi Naragani 7,935 Reputation points Microsoft External Staff Moderator

2025-05-13T14:02:29.2866667+00:00
@Sivaprasad Chidambaram,

Even though eastus is allowed in your policy, Azure Static Web Apps may not expose that region directly in the dropdown or use a corresponding API region like East US 2 under the hood. As you've noticed:

Choosing East US 2 worked for you because Azure internally maps resources that way.

Any mismatch (even within the same broader geography like "East US") can still result in a policy violation if it doesn't exactly match the allowed list.

This is due to how Azure evaluates resource group-level policy vs. service-specific region mappings.

To ensure successful Static Web App deployments under region restriction policies:

Align your allowed regions in policy with the actual regions offered in the Static Web App UI or CLI. For example, instead of just allowing eastus, also consider allowing eastus2, centralus, etc. if your governance policies permit.

If using automation (like CLI), explicitly choose a region that appears in your Azure Policy’s allowed list, and the Static Web App supported regions list.

Maintain a mapping table internally between allowed policy regions and the Azure service-specific regions that your teams use frequently.

Thank you for bringing this insight forward, it’ll be helpful for others facing similar restrictions. Let me know if you have any further concerns or queries

Share via

Error in creating Static Web App with location restriction policy

0 additional answers

Your answer