Find Microsoft Azure credentials for use in Orion Platform products

11/13/2018 3:20 AM

9/9/2022 9:05 PM

As you work with Microsoft Azure cloud services while using Orion Platform products (for example, to configure cloud monitoring or add API pollers), you may be prompted to provide different types of credentials, such as: 

• Subscription IDs

• Tenant/Directory IDs

• Client/Application IDs

• Application Secret Keys

The following table provides details about various types of Azure credentials. Note that the Azure user interface (UI) and documentation may use different phrases for the same type of credentials.
 

Credential	May also be called	Notes
Subscription ID	--	A globally unique identifier (GUID) that identifies your subscription to use Azure services and is used by Microsoft to manage billing. To find in the Azure Portal, refer to Microsoft's Azure portal documentation. Each deployed resource is linked to a single subscription.
Tenant ID	Directory ID	A GUID that represents the Azure AD directory where a registered application was created. To find in Azure, click Azure Active Directory service > App registrations > Your App >Directory (tenant) ID. Another way to access Subscription and Tenant IDs is to log into Azure, click the Help icon, click Show Diagnostics, and retrieve IDs from the JSON file. To create a Tenant ID, see Use the portal to create an Azure AD application and service principal that can access resources. An example of Tenant ID in an Access Token URL for an API poller is: https://login.microsoftonline.com/{{tenantId}}/oauth2/v2.0/token
Client ID	Application ID Application (client) ID Application Key	A unique ID generated by Azure Active Directory that is tied to an application and service principal during its initial provisioning. To find in Azure, click Azure Active Directory service > App registrations > Your App. See Getting an Application ID and authentication key .
Client Secret	Application Secret Key Client Secret Key	Used to secure access within the Azure Portal. To find in Azure, click Azure Active Directory service > App registrations > Certificates & secrets. See Create a new application secret. Important: When you generate a secret key, record it immediately so you don't have to create a new key later.

 

 
Azure permissions

In addition to credentials, Azure accounts require sufficient Azure Active Directory (AD) permissions. Azure uses role-based access control with a resource.operation.constraint pattern, as shown in these examples:

• ServiceHealth.Read grants access to read service health information in the Office 365 Management API.
• Reports.Read.All grants access to read usage reports in the Microsoft Graph API.

Recommended: Work with your organization's Azure Administrator to configure Azure permissions. SolarWinds Technical Support cannot assist with permission-related issues related to third-party products, such as Azure, due to variations in customer environments and Program Limitations.

The following figure shows Reports.Read.All permissions configured in Azure for an API poller based on the Microsoft 365 Teams API poller template:



When configuring Azure permissions, use Application nstead of Delegate as the Type for Microsoft Graph and Office 365 Management APIs.

To learn more, see Use the portal to create an Azure AD application and service principal that can access resources.

(Excerpts and figures in this section are attributed to © 2021 Microsoft Corp., available at docs.microsoft.com , obtained on June 15, 2021.)

Server Application Monitor