You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/governance/service-groups/manage-service-groups.md
+12-14Lines changed: 12 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,24 +1,22 @@
1
1
---
2
-
title: Manage Azure Service Groups
2
+
title: Manage Resouces Across Subscriptions and Resource Groups with Azure Service Groups
3
3
description: "Learn how to create, update, read, and delete Azure Service Groups and its members"
4
4
author: rthorn17
5
5
ms.author: rithorn
6
-
ms.service: Service Groups
7
-
ms.topic: overview #Don't change
6
+
ms.service: governance ## is service-groups going to be an official service slug?
7
+
ms.topic: how-to
8
8
ms.date: 05/19/2025
9
9
---
10
10
11
-
# How to manage Azure Service Groups?
11
+
# How to use Azure Service Groups to manage resources
12
12
13
-
Service groups in Azure are a low-privilege-based grouping of resources across subscriptions. They provide a way to manage resources with minimal permissions, ensuring that resources can be grouped and managed without granting excessive access. This article helps you learn how to manage Service Groups and its members.
13
+
You can group resources, across subscriptions, by creating Azure Service Groups. They provide a way to manage resources with minimal permissions, ensuring that resources can be grouped and managed without granting excessive access. This article helps you learn how to manage Service Groups and its members.
14
14
15
15
For more information on service groups, see [Getting started with Service Groups](overview.md).
16
16
17
-
> ![IMPORTANT]
18
-
> Service Groups are currently in a Limited Preview state and require Tenant onboarding before trial. To request for onboarding please see [TBD Link]().
19
-
>
20
-
> This documentation will show how to manage service groups and its members using the Azure portal and REST APIs in the Preview. CLI/ PowerShell/ Terraform support will be announced in a later release.
21
-
17
+
> [!IMPORTANT]
18
+
> Service Groups is currently in PREVIEW. For more information about participating in the preview, see [TBD Link]().
19
+
> See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for legal terms that apply to Azure features that are in beta, preview, or otherwise not yet released into general availability.
22
20
23
21
24
22
## Service Group Actions
@@ -32,7 +30,7 @@ This section shows you how to manage service group's actions create, read, updat
Copy file name to clipboardExpand all lines: articles/governance/service-groups/overview.md
+12-11Lines changed: 12 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,11 +18,20 @@ Service groups in Azure are a low-privilege-based grouping of resources across s
18
18
19
19
20
20
## Key capabilities
21
-
***Flexible Membership**: Service Groups allow resources from different subscriptions to be grouped together, providing a unified view and management capabilities. They also allow the grouping of subscriptions, resource groups, and resources.
22
-
***Low Privilege Management**: Service Groups are designed to operate with minimal permissions, ensuring that users can manage resources without needing excessive access rights.
23
-
***Multiple Hierarchies**: Service Groups live outside of the resource hierarchy enabling scenarios where the same resources need to be group for different purposes.
21
+
-**Multiple Hierarchies**: Service Groups live outside of the resource hierarchy enabling scenarios where the same resources need to be group for different purposes.*
22
+
-**Flexible Membership**: Service Groups allow resources from different subscriptions to be grouped together, providing a unified view and management capabilities. They also allow the grouping of subscriptions, resource groups, and resources.
23
+
-**Low Privilege Management**: Service Groups are designed to operate with minimal permissions, ensuring that users can manage resources without needing excessive access rights.
24
24
25
25
26
+
### Multiple Hierarchies
27
+
The same resources can be connected to many different service groups allowing different customer personas and scenarios to be created and used. With different Role Based Access Controls being assigned to the multiple Service Groups, customers can create many different views that support how they organize their resources.
28
+
29
+
#### Example Scenarios
30
+
* Separate Personas
31
+
* An issue that arose frequently when trying to adopt a strict hierarchy was who would own the parent items. With Service Groups, this situation no longer becomes an issue and the different personas can have their own individual views. Customers can use the same resources to be members of a Workload Service Group, a Department Service Group, and a Service Group with all Production resources.
32
+
33
+

34
+
26
35
### Flexible Membership
27
36
Within the hierarchy of resources, there's a limitation of one parent resource container to many children. For example, a resource can only be a member of one resource group or a resource group can only be a member of one subscription. Service Groups introduce a new model that allows a resources or resource containers to have memberships with multiple different Service Groups. The Service Group allows new scenarios where the same resources can be connected to many Service Groups Trees enabling new ways to view your data.
28
37
@@ -41,14 +50,6 @@ Service Groups don't have the same inheritance capabilities that other Azure Res
41
50
* Aggregating monitoring metrics
42
51
* 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.
43
52
44
-
### Multiple Hierarchies
45
-
The same resources can be connected to many different service groups allowing different customer personas and scenarios to be created and used. With different Role Based Access Controls being assigned to the multiple Service Groups, customers can create many different views that support how they organize their resources.
46
-
47
-
#### Example Scenarios
48
-
* Separate Personas
49
-
* An issue that arose frequently when trying to adopt a strict hierarchy was who would own the parent items. With Service Groups, this situation no longer becomes an issue and the different personas can have their own individual views. Customers can use the same resources to be members of a Workload Service Group, a Department Service Group, and a Service Group with all Production resources.
50
-
51
-

52
53
53
54
## How it works
54
55
Azure Service Groups are a separate hierarchy grouping resources that don't exist in the resource hierarchy with Resource Groups, Subscriptions, and Management Groups. The separation allows Service Groups to be connected many times to different resources and resource containers without impacting the existing structures.
0 commit comments