|
<< Click to Display Table of Contents >> Raynet One Data Hub > 2026.4 > Connectors > Alphabetic Connector List > Microsoft Azure Cost Details Prerequisites |
Before configuring the Microsoft Azure Cost Details connector, ensure that all of the following requirements are met.
The Microsoft Azure Cost Details connector is supported only for customers with one of the following agreement types:
•Enterprise Agreement (EA)
•Microsoft Customer Agreement (MCA)
The following subscription types are not supported: Pay-as-you-go, Visual Studio, and MSDN subscriptions. If you have one of these subscription types, use the Microsoft Azure Consumption connector instead.
The connector authenticates using OAuth 2.0 client credentials (application identity). No user login or multi-factor authentication is involved. You must register an application in Microsoft Entra ID (formerly Azure Active Directory) and obtain the following values:
•Tenant ID — the Directory (tenant) ID of your Azure Active Directory
•Client ID — the Application (client) ID of the registered application
•Client Secret — a client secret generated for the registered application
To register the application, sign in to the Azure portal, navigate to Microsoft Entra ID > App registrations > New registration, provide a name for the application, and select Register. After registration, generate a client secret under Certificates & secrets > New client secret. Record the secret value immediately, as it is not displayed again.
The registered application must be granted permission to call the Azure Cost Management API on the target billing scope. Contact your Azure billing administrator to assign the appropriate Billing role or Azure RBAC role on the billing account, billing profile, or subscription that you intend to query.
Note: The exact Billing role or RBAC permission required for the Cost Details API is pending Engineering confirmation. Consult your Azure billing documentation or contact Raynet support for the current permission requirement before assigning access.
Each connector instance is configured for exactly one billing scope and one Azure tenant. The scope is an Azure Resource Manager (ARM) Resource ID specifying the billing account, billing profile, invoice section, or subscription from which cost data is retrieved. Examples of valid scope formats:
•Billing account scope: /providers/Microsoft.Billing/billingAccounts/12345
•Subscription scope: /subscriptions/12345678-1234-5678-9012-123456789012
To collect data from multiple tenants or billing scopes, configure a separate connector instance for each.
The connector requires outbound HTTPS (port 443) access from the Data Hub server to the following Microsoft endpoints:
•login.microsoftonline.com — Azure AD OAuth 2.0 token endpoint
•management.azure.com — Azure Resource Manager (Cost Management API)
•Azure Storage blob endpoints — used to download the generated cost report (the exact host is returned dynamically by the API)
Note on Custom CA Certificates: If your network uses a custom TLS inspection certificate, you can provide the PEM-encoded CA certificate in the Certificate connector parameter. This certificate is used solely for TLS verification of outbound connections and is not a client authentication certificate.