Dynamics NAV 2017 as an App in Azure Management Portal

In Dynamics NAV 2017, you can use the Set Up Azure Management Portal guide to register Dynamics NAV in the Azure Management Portal and extract the information you need to use services such as the Sales and Inventory Forecast extension, Power BI, Office 365, and so on. The point of the registration is that Dynamics NAV and the service that you want to connect to must know the Azure Active Directory (Azure AD) details about each other. You must register in the Azure Management Portal only once, and you must be an administrator or superuser in Dynamics NAV plus log in to the Azure Management Portal as the Office 365 administrator.

If you use the Dynamics NAV 2017 image in the Azure Gallery, the script to deploy a demo environment has been updated to register correctly. For more information, see Freddy Kristiansen's blog post here (and follow his blog in general): https://blogs.msdn.microsoft.com/freddyk/2016/11/12/updates-to-the-azure-gallery-image-kind-of/

If you want to use services such as embedded Power BI and the new Outlook add-ins in your on-premises deployment, the Azure AD Application Setup wizard helps you register your solution in the Azure Management Portal. Also, a topic on Help Server called How to: Register Dynamics NAV in the Azure Management Portal explains the process.  However, after step 8, it misses an important piece of information: Give the relevant services access to your app.

The following section explains the steps required to register your Dynamics NAV deployment so that you can use services such as Power BI, Power Apps, Flow, and so on.

To register Dynamics NAV in the Azure Management Portal

  1. Log in to the Azure Management Portal at https://portal.azure.com. Log in as the administrator of your Office 365 tenant.
    If you are not familiar with the Azure Management Portal, you can find guidance in the Azure documentation library.
  2. In the left navigation pane, choose More services, and then choose App registrations.
  3. In the top menu, choose Add, and then, in the Create pane, fill in the fields with the following information:
    - Name: Specify a name for your Dynamics NAV solution, such as Dynamics NAV.
    - Application Type: Choose Web app / API.
    - Sign-on URL: Enter the URL for your Dynamics NAV browser client, such as https://MyServer:8080/DynamicsNAV/WebClient/OAuthLanding.htm.
    The OAuthLanding.htm file is a file that helps manage the exchange of data between Dynamics NAV and other services through Azure AD.
  4. Choose the Create button.
    This adds your Dynamics NAV to the App registrations pane, so you can now add settings to it.
  5. In the App registrations list, choose your new app. If this does not open the Settings pane, you should see an action to open Settings.
  6. In the Settings pane, in the API Access section, choose Keys.
  7. In the Keys pane, specify a description and when you want to let the key expire, and then choose Save.
  8. Copy the generated key to a temporary location - you will need it in the Azure AD Application Setup wizard in Dynamics NAV.
  9. In the API Access section, choose Required Permissions.
    • Add delegated permissions to view all reports to the Power BI Service
    • Add delegated permissions to Sign In and read user profile to Windows Azure Active Directory
  10. Close the Settings pane, and then, in the Essentials pane, copy the value of the Application ID to a temporary location.
Comments (6)
  1. anand says:

    While setup azure active directory system in nav 2017, it shows reply url in my case that is -http://mypcname:48900/DynamicsNAV/WebClient/OAuthLanding.htm
    I dont know from where port 48900 is coming and this link is not even working on my pc, because nav is working on 8080 port in my system. How to change this 48900 port to 8080 ? I am using this reply url as sign-on url. Am i right?

  2. alexr says:

    I have the same result than anad, and no more access with this link http://mypcname:48900.
    I’m wondering if we can use this from a local machine.

    1. anand says:

      this link https://www.youtube.com/watch?v=OcB4Ven91Ns shows how to integrate nav 2017 with powerw bi. Notice the url it uses, he is using cloud storage not local machine url. I guess we cant use this from local machine. You got something regarding this ?

  3. Mirce says:


    im trying to enable powerbi reports in Nav2017,

    first of all i registered the application in Azure AD then i go to Get started with power bi and then Authorize Azure Services the authorization is sucessfull message appear, but then after i close the window, message appears the Azure AD Authentication Flow provider is not initialized

    1. Joe Stadler says:

      If you get the error message “Azure AD Authentication Flow Provider not initialized” just check table 6303. There Codeunit ID 6303 and 9010 must be defined.

Comments are closed.

Skip to main content