Failure: Build & deploy Next.js app to Azure Web App

[justinbeadleelevate]

Hello,

• I stood up an instance of Azure Chat without issue in late 2023.
• I decided to do a clean implementation today so I disconnected my 2023 fork and archived my repository.
• I forked Azure Chat again, deployed the Azure resources, etc.
• Now when I try to deploy my code from Github to Azure, I get the following failure error: "Login failed with Error: Not all parameters are provided in 'creds'. Double-check if all keys are defined in 'creds': 'clientId', 'clientSecret', 'tenantId'.. Double check if the 'auth-type' is correct."
• I've double, triple, and quadruple-checked my app registration, service principal JSON output and secrets in Github, etc.

I can't figure out why this worked so smoothly back in 2023 but now I'm running into problems. Any assistance will be greatly appreciated.

[olafwrieden]

Hi @justinbeadleelevate maybe not a straightforward answer but some pointers. Can you confirm:

• That you are using a new Service Principal as the secret for the old one (from you prior implementation) may not have the right permissions or has expired (defaults to 1yr validity but can be changed using the --years n flag - doc).
• That the two GitHub secrets were created in the right place under Your Forked Repo's Settings > Secrets and Variables > Actions > Repository Secrets? Placing it under the Codespaces won't work, it must be an Actions repo secret.
  Screenshot of location where the two secrets should be configured:
  
• That the name of the secret is: AZURE_CREDENTIALS and AZURE_APP_SERVICE_NAME respectively per the docs.
• There was a deprecation warning with the --sdk-auth flag when creating the Service Principal, have a quick read of this comment which describes the expected format of the GitHub secret, then ensure that the value for AZURE_CREDENTIALS in fact adheres to the expected JSON structure:

  {
    "clientId": "<Client ID>",
    "clientSecret": "<Client Secret>",
    "subscriptionId": "<Subscription ID>",
    "tenantId": "<Tenant ID>"
  }