Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. In the Microsoft Azure portal, click All Services.
  2. Search for “Azure Active Directory” and click to open Azure Active Directory.
  3. Click App Registrations in the left panel.
  4. In the App registrations panel, either select an existing discovery application or click + New registration to add a new application.
  5. If you are adding a new application, enter the following to define your application in the Create wizard, and then
    click Create to add the application.
    Name: Enter the name of your new application.
    — Supported account types: Select the account type.
    — Redirect URI: Ensure that you use a unique URL for sign-on purposes.
    Azure notifies you when the application is successfully created.


    Note
    titleNote

    To obtain token information for the endpoints, click the Endpoints icon next to + New registration in the App registration panel. Azure displays the Endpoints page that contains endpoint information for the discovery application. vDiscovery uses the OAUTH 2.0 TOKEN ENDPOINT (the second last item on the list). Copy the link from the table. You use this information to define the vDiscovery endpoint in NIOS. The token corresponds to the Service Endpoint field in NIOS.


  6. Select and click the application from the list. The Azure portal displays details about your application, such as Display nameApplication IDDirectory ID, and Object ID. Click API permissions in the left panel, and then click + Add a permission in the API Permissions panel.

    Note
    titleNote

    Ensure that you copy the Application ID and save this value for future use. This ID is used as the Client ID in your vDiscovery configuration.

  7. In the Request API permissions panel, click APIs my organization uses.

  8. Select Windows Azure Service Management API from the list.

  9. Select Delegated permissions and Access Azure Service Management as organization users (preview) check box, and then click Add permission.

  10. In the left panel, click Certificates & secrets, and then click +New client secret:
    — Description: Enter a name or description for the generated key.
    — Expires: Select expiry time for the generated key.
    Value: The key will be displayed here after you select the duration and save the configuration.

    Note
    titleNote

    Copy the key and save it for your vDiscovery jobs. The key corresponds to the Client Secret in NIOS when you configure vDiscovery jobs.


  11. Validate all the configuration and information on this page. 

    Note
    titleNote

    The vDiscovery in Azure is performed on the subscription linked to the application.

  12. Navigate to All services -> Subscriptions.

  13. Click on the subscription name for your subscription.
  14. Click Access control (IAM).
  15. Click Add.
  16. Expand the Role drop-down menu and select Reader.
  17. In the Select box, type the name for your registered app, or locate and select it in the Selected members list.

  18. Click Save. You have completed the vDiscovery configuration in Azure.

Note
titleNote

You can assign multiple subscriptions for a vDiscovery job with one Client ID and one Client Secret.


To configure vDiscovery jobs in NIOS, you must record the following information from the Azure portal:

...