Troubleshooting: Running the Cmdlet for a Microsoft Dynamics NAV Web Server Hosted in Complex Network Topology

Setting the trust relationship between the Microsoft Dynamics NAV Web client and Microsoft Azure Active Directory requires specifying a remote endpoint for the Microsoft Dynamics NAV Web client in the Azure AD Service Principal that is created for this web application. If the Dynamics NAV Web server runs behind a DNS or another network component that changes or rewrites the web client’s address, the Set-NavSingleSignOnWithOffice365 cmdlet is not able to compute this address, since it only runs on the local computer. To fix this issue, you can provide the cmdlet with the address as seen remotely for your Microsoft Dynamics NAV Web client. The parameter you need to pass this address to is NavWebAddress.

See Also

How to: Set up Microsoft Dynamics NAV for Single Sign-on With Office 365 using Windows PowerShell
Authenticating Users with Azure Active Directory