Skip to content

Commit ad5c11a

Browse files
Merge pull request #309157 from v-albemi/warning-prerequisite
Add warning note and prerequisite to 3 articles
2 parents ce54a7f + c660a6e commit ad5c11a

3 files changed

Lines changed: 66 additions & 1 deletion

File tree

articles/partner-solutions/dynatrace/manage.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -92,6 +92,22 @@ To monitor resources for Azure Arc Machines, select **Dynatrace environment conf
9292

9393
## Monitor multiple subscriptions
9494

95+
When you add or remove subscriptions for Dynatrace monitoring, the system updates the Monitoring Reader role assignment on the system-managed identity that's linked to the resource.
96+
97+
### Prerequisites
98+
99+
- To perform these actions, you must have both of the following Azure permissions:
100+
101+
- `Microsoft.Authorization/roleAssignments/write`
102+
- `Microsoft.Authorization/roleAssignments/delete`
103+
104+
- The resource provider for Dynatrace (Dynatrace.Observability) must be registered in the target subscription.
105+
106+
### Add subscriptions
107+
108+
> [!IMPORTANT]
109+
> When you link a subscription to a Dynatrace resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md).
110+
95111
To monitor multiple subscriptions:
96112

97113
1. In the left pane, select **Dynatrace environment config** > **Monitored Subscriptions**.
@@ -118,6 +134,9 @@ After a subscription is added, the status changes to **Active**.
118134

119135
## Remove subscriptions
120136

137+
> [!IMPORTANT]
138+
> When you unlink a subscription from a Dynatrace resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md). 
139+
121140
To unlink subscriptions from a Dynatrace resource:
122141

123142
1. Select **Dynatrace environment config** > **Monitored Subscriptions** in the left pane.

articles/partner-solutions/elastic/manage.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -218,6 +218,20 @@ To view the list of resources emitting logs to Elastic, select **Elastic deploym
218218
219219
## Monitor multiple subscriptions
220220

221+
### Prerequisites
222+
223+
- To perform these actions, you must have both of the following Azure permissions:
224+
225+
- `Microsoft.Authorization/roleAssignments/write`
226+
- `Microsoft.Authorization/roleAssignments/delete`
227+
228+
- The resource provider for Elastic (Elastic.Observability) must be registered in the target subscription.
229+
230+
### Add subscriptions
231+
232+
> [!IMPORTANT]
233+
> When you link a subscription to an Elastic resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md).
234+
221235
To monitor multiple subscriptions:
222236

223237
1. Select **Elastic deployment configuration** > **Monitored Subscriptions**.
@@ -239,6 +253,9 @@ Once the subscription is added, the status changes to *Active*.
239253

240254
### Remove subscriptions
241255

256+
> [!IMPORTANT]
257+
> When you unlink a subscription from an Elastic resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md). 
258+
242259
To unlink subscriptions from an Elastic resource:
243260

244261
1. Select **Elastic deployment configuration** > **Monitored Subscriptions** from the service menu.

articles/partner-solutions/new-relic/manage.md

Lines changed: 30 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,23 @@ The column **Logs to New Relic** indicates whether the resource is sending logs
6666

6767
## Monitor multiple subscriptions
6868

69-
You can now monitor all your subscriptions through a single New Relic resource using **Monitored Subscriptions**. You don't have to set up a New Relic resource in every subscription that you intend to monitor. Instead, monitor multiple subscriptions by linking them to a single New Relic resource tied to a New Relic organization to view all resources across multiple subscriptions from a single pane.
69+
You can monitor all your subscriptions through a single New Relic resource by using **Monitored Subscriptions**. You don't have to set up a New Relic resource in every subscription that you intend to monitor. Instead, monitor multiple subscriptions by linking them to a single New Relic resource tied to a New Relic organization to view all resources across multiple subscriptions from a single pane.
70+
71+
When you add or remove subscriptions for New Relic monitoring, the system updates the Monitoring Reader role assignment on the system-managed identity that's linked to the resource.
72+
73+
### Prerequisites
74+
75+
- To perform these actions, you must have both of the following Azure permissions:
76+
77+
- `Microsoft.Authorization/roleAssignments/write`
78+
- `Microsoft.Authorization/roleAssignments/delete`
79+
80+
- The resource provider for New Relic (NewRelic.Observability) must be registered in the target subscription.
81+
82+
### Add subscriptions
83+
84+
> [!IMPORTANT]
85+
> When you link a subscription to a New Relic resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md).
7086
7187
To monitor multiple subscriptions:
7288

@@ -89,6 +105,19 @@ If you have existing New Relic resources that are linked to the account for moni
89105

90106
The tag rules and logs that you defined for the New Relic resource apply to all the subscriptions that you select to be monitored.
91107

108+
### Remove subscriptions
109+
110+
> [!IMPORTANT]
111+
> When you unlink a subscription from a New Relic resource, ensure that the subscription isn't scope locked (read-only or delete locks). Scope locks can prevent the addition and removal of diagnostic settings. For more information, see [Lock your Azure resources](../../azure-resource-manager/management/lock-resources.md). 
112+
113+
To unlink subscriptions from a New Relic resource:
114+
115+
1. Select **New Relic account config** > **Monitored Subscriptions** from the service menu.
116+
1. Select the subscription you want to remove.
117+
1. Select **Remove subscriptions**.
118+
119+
To view the updated list of monitored subscriptions, select **Refresh** from the Command bar.
120+
92121
## Connected New Relic resources
93122

94123
To view and manage all your New Relic Resources, select **New Relic account config** > **Connected New Relic Resources** from the *Service menu*.

0 commit comments

Comments
 (0)