D365 F&O PROD Login Issue

The error indicates a sign‑in/authorization problem for Finance & Operations. For an on‑premises or AD FS–backed deployment, use the following checks and fixes.

1. Verify provisioning values in Service Fabric Explorer
   • In Service Fabric Explorer, open Cluster → Applications → AXSFType → fabric:/AXSF Details.
   • Confirm that:
     • Provisioning_AdminPrincipalName is the correct admin UPN.
     • Provisioning_AdminIdentityProvider is the correct identity provider.
   • If these values are invalid, correct them and redeploy as per internal procedures.
2. Reset database users and AOS services
   • On the primary SQL Server machine, run:

          .\Reset-DatabaseUsers.ps1
     

   • On each AOS machine, open Task Manager, select AXService.exe, and choose End task to restart the AOS service.
3. Verify the admin user record in AXDB
   • In SQL Server Management Studio, run this query against the AXDB database:

          select SID, NETWORKDOMAIN, NETWORKALIAS, * 
          from AXDB.dbo.USERINFO 
          where id = 'admin'
     

   • Confirm that NETWORKDOMAIN and identity provider values match the AD FS/Microsoft Entra configuration for the admin account.
4. Check AD FS federation settings If the message persists ("You are not authorized to login with your current credentials"), validate AD FS configuration:
   • On the AD FS server:
     1. Open Server Manager → Tools → AD FS Management.
     2. Right‑click AD FS → Edit Federation Service Properties.
     3. Ensure Federation Service Identifier matches UserInfo.NetworkDomain and UserInfo.IdentityProvider in AXDB.
     4. In PowerShell, run Get-AdfsProperties and confirm:
        • IdTokenIssuer equals the Federation Service Identifier.
        • IdTokenIssuer also matches Provisioning_AdminIdentityProvider on the fabric:/AXSF Details tab in Service Fabric Explorer.
   • Re‑test login after any corrections.

If these steps do not resolve the issue, follow the AD FS–specific troubleshooting guidance referenced in the on‑premises deployment article.

References:

• Troubleshoot on-premises deployments