Skip to content

Commit b8f131d

Browse files
Merge pull request #307188 from kenieva/patch-17
Revise example scenarios for Service Groups
2 parents 864f0dd + 7c5c928 commit b8f131d

1 file changed

Lines changed: 4 additions & 4 deletions

File tree

articles/governance/service-groups/overview.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -26,11 +26,11 @@ Azure Service Groups offer a flexible way to organize and manage resources acros
2626

2727

2828
### Example Scenarios
29-
Customers can create many different views that support how they organize their resources.
29+
Customers can create many different views that support how they organize their resources.
3030

31-
* Aggregating Metrics
32-
* Organizations with multiple applications and environments can use Service Groups to aggregate metrics across different environments. Member resources or resource containers could be from various environments within different management groups or subscriptions, can be linked to a single Service Group providing a unified view of metrics.
33-
* Since Service Groups don't inherit permissions to the members, customers can apply least privileges to assign permissions on the Service Groups that allow viewing of metrics. This capability provides a solution where two users can be assigned access to the same Service Group, but only one is allowed to see certain resources.
31+
* Unified View of Resources
32+
* Organizations with multiple applications and environments can use Service Groups to create a centralized view of resource information across different environments. Member resources or resource containers from various environments within different management groups or subscriptions can be linked to a single Service Group, providing a unified reference point for resource details.
33+
* Since Service Groups dont inherit permissions from their members, customers can apply least-privilege principles to assign permissions on the Service Groups that allow viewing of resource information. This capability enables scenarios where two users can access the same Service Group, but only one is allowed to see certain resources.
3434

3535
* Creating Inventory
3636
* Customers can connect resources to the Service Groups to get a consolidated view of all the resources of a particular type or function in the entire environment.

0 commit comments

Comments
 (0)