- Microsoft Graph APIs
- Azure Management APIs
- Microsoft 365 data
- Azure subscription data
Overview of What You’ll Configure
You will:- Retrieve your Tenant ID
- Register an Azure AD application
- Generate a client secret
- Configure API permissions
- Assign Azure RBAC permissions (Reader role)
- Add required secrets to Configview
Step 1: Retrieve Your Tenant ID
- Go to Microsoft Entra ID
https://portal.azure.com/#view/Microsoft_AAD_IAM/ActiveDirectoryMenuBlade/~/Overview - Copy the Tenant ID from the Overview page.
- In Configview Secrets, paste it into:
- Click Save.
Step 2: Register a New Application
- Go to the Azure Portal
https://portal.azure.com/ - Navigate to:
Microsoft Entra ID → App registrations - Click New registration
- Configure:
- Name: Configview (or similar)
- Supported account types: Single tenant
- Redirect URI: Optional (not required for client credential flow)
- Click Register
Step 3: Create a Client Secret
- In your registered application, go to Certificates & Secrets.
- Under Client Secrets, click New client secret.
- Configure:
- Description: Configview
- Expiration: 1–2 years recommended
- Click Add.
- Immediately copy the Value (NOT the Secret ID).
Step 4: Configure Microsoft Graph API Permissions
- Expand Managed > API Permissions.
- Click Add a permission.
- Select Microsoft Graph.
- Choose Application permissions (not Delegated).
Copy and paste them in the select permissions window
- Application.Read.All
- BitlockerKey.Read.All
- Directory.Read.All
- Domain.Read.All
- LicenseAssignment.Read.All
- MailboxSettings.Read
- MultiTenantOrganization.Read.All
- Policy.Read.All
- User.Read.All
- DeviceManagementManagedDevices.Read.All
- **Click Add Permissions **
- Grant admin consent Check. Yes to confirm
- Remove the delegated permission for User.Read Delegated
Step 1 — Go to:
Azure Portal →Subscriptions →
Select your subscription →
Step 2 — Click:
Access Control (IAM)Step 3 — Add Role Assignment
Assign your App Registration (Service Principal) one of these roles:- Reader (read-only)
Step 5: Assign Reader Role in Azure
(Required for Azure Data) This must be done for each subscription, or once at the Root Management Group (recommended).Assign at Root Management Group
- Go to Resource Manager
- **Expand Organization **
- Click Management Groups.
- Select your Tenant Root Group.
- Go to Access control (IAM).
- Click Add → Add role assignment.
- Role: Reader
- Assign access to: application you created
- Click Review and assign Save.
Step 7: Configure Required Secrets in Configview
Add the following secrets in the Configview Secrets manager.Make sure values are entered exactly as shown.
| Secret | Value | Notes |
|---|---|---|
| MSFT_SCOPE | https://graph.microsoft.com/.default | Must match exactly |
| MSFT_AZURE_SCOPE | https://management.azure.com/.default | Must match exactly |
| MSFT_TOKEN_URL | https://login.microsoftonline.com/{tenant_id}/oauth2/v2.0/token | Replace {tenant_id} with your Tenant ID |
| MSFT_TENANT_ID | Your Tenant ID | Microsoft Entra ID → Overview |
| MSFT_CLIENT_ID | Application (client) ID | From App Registration |
| MSFT_CLIENT_SECRET_ID | Client Secret Value | Certificates & Secrets → Secret Value (not Secret ID) |
Important Notes
- Always select Application permissions, not Delegated.
- Admin consent is required after adding permissions.
- Client secret values cannot be retrieved after creation.
- Reader role assignment is required for Azure subscription ingestion.
- Assigning at the Root Management Group applies to all subscriptions beneath it.