[Bicep/ARM] Cannot set custom domain

[sinedied]

Describe the bug

I'm trying to create a SWA from scratch using Bicep, and setting custom domains the same way.

My template looks like this for the SWA part:

resource staticWebApp 'Microsoft.Web/staticSites@2021-01-15' = {
  name: '${appName}-staticwebapp${dashSuffix}'
  location: location
  sku: {
    name: 'Standard'
    tier: 'Standard'
  }
  properties: {
    repositoryUrl: 'https://github.com/${githubRepo}'
    branch: 'main'
    provider: 'GitHub'
    repositoryToken: githubToken
    buildProperties: {
      appLocation: '/'
      apiLocation: ''
      outputLocation: 'dist/${projectName}'
      skipGithubActionWorkflowGeneration: true
      githubActionSecretNameOverride: 'AZURE_SWA_TOKEN'
    }
    stagingEnvironmentPolicy: 'Enabled'
    allowConfigFileUpdates: true
    userProvidedFunctionApps: [
      {
          functionAppResourceId: functionApp.id
          functionAppRegion: location
      }
    ]
  }
  dependsOn: [
    functionApp
  ]

  resource staticWebAppDomains 'customDomains@2021-01-15' = [for domain in domains: {
    name: domain
    properties: {
      validationMethod: 'dns-txt-token'
    }    
  }]
}

I would like to use TXT validation for validating the domain names, as seen here in the template. I have 2 issues doing that:

• I don't know how to get the generated token code, so I can put in the Azure DNS template. I found nothing related in the docs.

• The Bicep template without the customDomains part works fine. But when I add the customDomains section, it never returns and seems to get stuck (waiting for the validation to succeed?). When I break out of the deployment (with CRTL+C) as it's waiting forever, get an error when I'm trying to redeploy because the previous deployment never ended:

  {"error":{"code":"DeploymentActive","message":"Unable to edit or replace deployment 'poc': previous deployment from '10/12/2021 12:33:34 PM' is still active (expiration time is '10/19/2021 12:28:14 PM'). Please see https://aka.ms/arm-deploy for usage details."}}

  I have to cancel the deployment manually otherwise it gets stuck for days.

Note that I'm deploying the bicep template with az deployment group create.

Expected behavior

Adding customDomains resources to my SWA Bicep template should work without getting stuck in the process, and I should be able to retrieve the generated validation codes to use then in the Azure DNS part of the Bicep template.

Additional info:

I should mention that the custom domain are correctly set, as I can see them in the Azure portal, in the custom domains section of the deployed SWA, waiting on "validating" message.

[abouroubi]

Is there any new on this ? Can't seem to find any documentation regarding how to fill the validation method

[trondjun]

Did you find a way to get through the validation of custom domain?

I have the same issue now, and it just gets stuck on validating.

[sinedied]

Currently there's no solution, but the team is looking at it. cc @simonaco

[trondjun]

Great! If there is anything I can provide to help, let me know!

[chrisjensenuk]

We've just hit this issue too. Any update on this? Thanks

[AnthonyPhan]

same issue here, any updates?

[Gertray13]

Same issue here. Does someone has a workaround?

[larsmaes-sogeti]

Same problem here, still no workaround?

[abouroubi]

Looks like they don't care, this product is half baked, it was made in a hurry as an answer to AWS Amplify.

[larsmaes-sogeti]

It ssems to be somewhat related to: https://github.com/Azure/bicep/issues/4483

[andrem0]

No progress here? @simonaco @sinedied

[sinedied]

Simona isn't working on the team anymore, and I don't have any news regarding this. Maybe @anthonychu have an update on this, as it's likely to concern all App Services products?

[LarsKemmann]

Anything? Any update at all? It's been almost two years for a basic automation ask.

[TheCloudWarrior]

Anything? Any update at all? It's been almost two years for a basic automation ask.

I think its a bit weird that someone has left the team and apparently all work has stopped. Just look at the Github issues.

Anyways, the only way I have found this works is to use a deployment script to make an API call to get the validationToken and then create a TXT record in your DNS. I do not like using deploymentScripts but I like copy/pasting TXT records even less... I have a little example here: https://github.com/TheCloudWarrior/AzureStaticWebApp

I hope I have taken out all hardcoded variables :)