Hi,
If you run the Assisted Setup, you can connect to Azure AD. Here you authenticate yourself. If you did run this before with incorrect PublicWebBaseUrl, it will not do it again. Then you do need to correct it in Azure portal.
The PublicWebBaseUrl is like nav.yourdomain.com:port/.../
In the Azure AD App, a html file is added so that the landing page will become:
nav.yourdomain.com:port/.../OAuthLanding.htm
The Azure AD app is called (you can find it in App Registrations in Azure Portal, All Applications):
Microsoft Dynamics NAV Application
Personally, I do usually add the NST instance name to it so that it does become Microsoft Dynamics NAV Application BC140, this is however not required. In my scenario I do have multiple releases running on the same box which means multiple registrations. Here you will find two reply urls. The above one and the actual PublicWebBaseUrl plus /SignIn.
nav.yourdomain.com:port/.../OAuthLanding.htm
nav.yourdomain.com:port/.../SignIn
Earlier I did mention that the SignInAudience of the created AD App must be AzureADMultipleOrgs. It does however create AzureADMyOrg. You can correct that in the Azure AD App manifest file (you can retrieve that via the browser).
Hope it does help.
Thanks.
Marco
