Fix Common Setup, Sign-In and Access Problems

What each Atlas AVD setup, sign-in and lock-screen message means and how to fix it: setup link errors, deployment problems, an expired client secret, and more.

On the setup page

  • Verification Failed: the setup link has expired or is no longer valid. Setup links work for 4 hours. Start your trial setup again at atlasavd.com/deploy for a fresh link.
  • Setup was not authorised or Setup did not complete: nothing was left behind in your directory. Click Run setup again with a Global Administrator account, or choose Set it up yourself with a script.
  • Could not start the Azure sign-in: wait a moment and try again, or use the Azure Portal wizard further down the page to deploy instead.
  • Deployment could not start: use the Azure Portal wizard instead. If the message says the Atlas app registration no longer exists in your Entra directory, run the Set Up Atlas Access step again. Deployment continues on the same page once it completes.
  • Can't check deployment status: your Azure sign-in may have expired, but the deployment may still be running in Azure. Try again, or start over to sign in and deploy afresh.
  • Your subscription has no quota for the region or size you picked: see Request an App Service Quota Increase. If Atlas can't file the request for you (Could not file the quota request), request it in the Azure portal under Help + Support.
  • Deployment failed: click Try again, or Cancel & clean up to remove what was created and start over.

On the sign-in page

These banners appear above the sign-in buttons. Most clear up if you simply sign in again.

  • Your sign-in session expired, Sign-in state was lost, or Microsoft did not return an authorization code: sign in again from the same browser tab, without switching browsers or using an old bookmark partway through.
  • Too many sign-in attempts: wait a minute, then try again.
  • This sign-in link uses a different web address than the one configured for this app: sign in at the address shown below the banner. If you moved Atlas to a custom domain, see Add a Custom Domain.
  • This account is not authorized: the account has no Atlas role. An Atlas administrator can add it (see Add Users & Assign Roles).
  • This account has been disabled: an Atlas administrator turned the account off. Ask them to turn it back on.
  • Sign-in isn't configured yet: the deployment is missing its app registration settings. Contact support@atlasavd.com.
  • Sign-in failed. Microsoft Entra rejected the client secret: the AtlasAVD app registration's client secret has expired or been replaced. Follow Replace an expired client secret below.

Replace an expired client secret

Setup gives the AtlasAVD app registration a client secret that lasts 2 years. When it expires, nobody can sign in until you add a new one. Your deployment reads the secret from the Key Vault in its resource group, so you replace it there.

  1. In the Microsoft Entra admin center, open App registrations → AtlasAVD → Certificates & secrets and click New client secret. Copy the Value straight away; it is shown only once.
  2. In the Azure portal, open the Key Vault in your Atlas AVD resource group, go to Secrets → ENTRA-CLIENT-SECRET, and click New Version. Paste the new value and save. You need permission to set secrets in that Key Vault.
  3. Restart the Atlas AVD App Service in the same resource group so it picks up the new value, then sign in again.
  4. If the same app registration is saved as a tenant's credentials in Atlas (Administration → Tenants → Tenant List), update the client secret there too.

Add the new secret before the old one expires and you avoid any downtime: both keep working until the old one runs out. Delete the old secret in Certificates & secrets once everyone can sign in.

When Atlas AVD is locked

A full-screen message replaces Atlas AVD when there is no active plan for your deployment. Nothing is deleted while it shows: your host pools, session hosts and settings stay in your own Azure subscription, and software updates stay available.

  • Your Atlas AVD trial has ended: click Choose your plan and check out with Stripe. If you have already paid, click I've already purchased — check now. It can take a few minutes after purchase for the subscription to be found.
  • Couldn't reach the licensing service: your deployment can't contact Atlas. Check its outbound internet access (firewall, proxy or network rules on the App Service), then check again.
  • Your Atlas AVD subscription has expired, or has been canceled: choose a plan to continue.
  • Your Atlas AVD subscription is suspended: a payment is outstanding, or your deployment hasn't been able to check its license with Atlas for several days. Pay the outstanding invoice or restore the connection, then check again.
  • Your Atlas AVD license has been revoked: contact Atlas AVD support.
  • Activate this deployment: your deployment isn't connected to Atlas yet, so it can't receive your plan. An administrator clicks Activate deployment, or opens Administration → Platform → License Overview → Activation Diagnostics, then chooses a plan.

Only administrators can choose a plan. Everyone else sees Ask an administrator on this deployment to select a plan.

Still stuck?

Email support@atlasavd.com with the message you see, the time it happened, and the Correlation ID if the sign-in page shows one. If Atlas AVD is running, you can also open a ticket from Administration → Support; Check Your Deployment's Health and Get Help Faster shows what to attach so we can help you quickly. If Atlas AVD won't start at all, see Recovery Mode.

Next steps