Skip to content

Commit 202e1f9

Browse files
Merge pull request #21464 from nr-ssahoo/monitoring_reader_at_subscription
updated the doc with the new permission needed
2 parents 03c0a74 + e2ccc6a commit 202e1f9

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/content/docs/infrastructure/microsoft-azure-integrations/get-started/activate-azure-integrations.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -121,6 +121,7 @@ Your app must provide `Reader` permissions for each Azure service you want New R
121121
7. On the Members tab, click <DNT>**+ Select members**</DNT>. Search for your New Relic application name (e.g., <DNT>**NewRelic-Integrations)**</DNT>, select it, and click the <DNT>**Select button**</DNT>.
122122
8. Click <DNT>**Review + assign**</DNT> to save the role.
123123
9. After the first role is saved, repeat the "Add role assignment" process to also assign the <DNT>**Monitoring Reader**</DNT> role to the same New Relic application.
124+
10. Ensure the <DNT>**Monitoring Reader**</DNT> role is assigned at the subscription level.
124125

125126
Some Azure services, including [Azure CosmosDB](/docs/infrastructure/amazon-integrations/aws-integrations-list/azure-document-dbcosmos-db) and [Azure VMs](/docs/infrastructure/microsoft-azure-integrations/getting-started/azure-vms-monitoring-integrations), require additional steps. See the [Azure integration documentation](/docs/integrations/microsoft-azure-integrations/azure-integrations-list) for the services you want to enable.
126127

0 commit comments

Comments
 (0)