Determining the Tenant/Directory ID and Application/client ID of the created Application

An Azure AD Application is a digital identity and some associated configuration, which informs Azure AD about how to treat software which uses that digital identity.

The eG agent can pull performance metrics related to an Azure tenant, its services, and its resources, only if it communicates with an Azure AD tenant as an ‘Application’ with ‘monitoring rights’.

If such an Application pre-exists with the target tenant, then you can configure the eG agent with the access credentials of that application. However, if no such application pre-exists, then first register a new Application with Azure AD and obtain the access tokens that Azure AD issues for that application.

To achieve this, do the following:

1. Login to Microsoft Azure portal using https://portal.azure.com with valid credentials.

2. When the portal opens, Click on the Azure Active Directory in the Azure services page.

3. When the Default directory page appears, click on the App Registrations option in its left pane.

4. App registrations page will then appear.

5. To register a new application, click the New registration option indicated in the App registrations page. The Register an application page will then appear.

6. In the Register an application page, specify the following:

   • The name of the application in the Name text box,

   • Select the type of the account from the Supported account types section.

     Supported account types	Description
     Accounts in this organizational directory only	Select this option if you want all user and guest accounts in your directory to use the application or API. Use this option if your target audience is internal to your organization.
     Accounts in any organizational directory	Select this option if you want all users with a work or school account from Microsoft to use this application or API. This includes schools and businesses that use Office 365.Use this option if your target audience is business or educational customers and to enable multitenancy.
     Accounts in any organizational directory and personal Microsoft accounts	Select this option if you want all users with a work or school, or personal Microsoft account to use your application or API. It includes schools and businesses that use Office 365 as well as personal accounts that are used to sign in to services like Xbox and Skype. Use this option to target the widest set of Microsoft identities and to enable multitenancy.
     Personal Microsoft Accounts only	Select this option if you want the application or API to be used by only those users with personal accounts that are used to sign in to services like Xbox and Skype.

   • Then, enter the redirect URl (or reply URL) for your application in the Redirect URI text box. Typically, you need to provide the base URL of your app. For example, http://localhost:31544 might be the URL for a web app running on your local machine. Users would use this URL to sign in to a web client application. For public client applications, provide the URL used by Azure AD to return token responses. Enter a value specific to your application, such as https://DocApp.com//auth.

7. Clicking the Register button in Register an application page will create the Application. Then, Monitor App page will appear displaying the Essentials related to the new Application.

8. From the Essentials, you can obtain the Application ID and Directory ID. Copy the Application ID and the Directory ID and paste them against the CLIENT ID and TENANT ID text boxes while configuring eG tests for the target Azure component.