Ce navigateur n’est plus pris en charge.
Effectuez une mise à niveau vers Microsoft Edge pour tirer parti des dernières fonctionnalités, des mises à jour de sécurité et du support technique.
I have a SWA infrastructure with a linked Function app (Flex Consumption Plan) function that does not provision (internal server error) when using Sweden Central Region. It deploys fines on East US2.
The error:
{"code":"DeploymentFailed","target":"/subscriptions/f62c776c-adc1-4feb-9ac7-94ea741452c7/resourceGroups/rg-yolasors-pizza/providers/Microsoft.Resources/deployments/registration-webapp","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/f62c776c-adc1-4feb-9ac7-94ea741452c7/resourceGroups/rg-yolasors-pizza/providers/Microsoft.Resources/deployments/jd5ou4lth2zjs-StaticSite-UserDefinedFunction","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/f62c776c-adc1-4feb-9ac7-94ea741452c7/resourceGroups/rg-yolasors-pizza/providers/Microsoft.Resources/deployments/jd5ou4lth2zjs-StaticSite-UserDefinedFunction","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"InternalServerError","message":"There was an unexpected InternalServerError. Please try again later. x-ms-correlation-request-id: d6684b9a9da5d6a0d423accd7ccf920d"}]}]}]}
I'm using Bicep with AVM and AZD CLI to provision this infra.
Plateforme et infrastructure de cloud computing pour la génération, le déploiement et la gestion d’applications et de services à travers un réseau mondial de centres de données gérés par Microsoft.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
we could see that Azure App Service – Static Web Apps (both Free and Standard SKUs) is not currently supported in Sweden Central, as shown in the official Azure Products by Region documentation .
Interestingly, the same deployment completes successfully when targeting East US2, which indicates that the issue is region-specific rather than template- or configuration-related.
Recommendation:
Please try deploying to other supported regions for SWA
My comment may have not been clear on that point:
the SWA app is ALWAYS deployed to eastus2, regardless of the other resources and RG region. However, this should only affect the built-in managed function which I don't use use, as SWA is global service otherwise.
It's when I deploy the other resources in a region other than eastus2 (like eastus, north europe or sweden central) that the issue occurs. The same bicep infra worked fine few weeks ago.
Thanks for your patience!
Since the Static Web App always goes to East US2 (which is expected), and the issue only happens when the Function App is in Sweden Central, it would be helpful to narrow things down a bit.
Can you try deploying just the Function App on its own in Sweden Central (without linking it to the SWA) and let us know if that works? If it fails, please share the error message or any logs you see.
This will help us figure out if the issue is with the Function App itself or something related to how it connects to the SWA.
Bonjour Yohan,
Notre communauté Q&A accepte aussi le français, pour des raisons de facilité de recherche pour les autres utilisateurs qui ne maîtrise pas l'anglais. Je vous invite à écrire l'ensemble de vos réponses en Français, s'il vous plaît.
Belle journée,
Bryx
Found the issue, the bicep AVM module I was using for SWA didn't use the same property to set the backend region as the ARM template, so it was using the wrong region.
This issue is solved,
Thanks for the update, and great catch on identifying the mismatch in how the backend region was being set in the Bicep AVM module versus the ARM template.