Merge pull request #1 from cynthn/patch-572531

rthorn17 · web-flow · commit bfa19b805bf2 · 2025-05-06T09:31:14.000-04:00
Sugestions for Service Groups overview.md
diff --git a/articles/governance/index.yml b/articles/governance/index.yml
@@ -40,6 +40,17 @@ productDirectory:
           text: Protect your resource hierarchy
         - url: ./management-groups/index.yml
           text: See more >
+    - title: Azure Service Groups
+      imageSrc: ./media/management-groups.svg
+      links:
+        - url: ./service-groups/overview.md
+          text: Developer overview
+        - url: ./service-groups/create-service-group-rest-api.md
+          text: Create a service group using the REST API
+        - url: ./service-groups/create-service-group-member-rest-api.md
+          text: Connect resources or resource containers to service groups 
+        - url: ./service-groups/manage-service-groups.md
+          text: Manage Service Groups
     - title: Azure Policy
       imageSrc: ./media/azure-policy.svg
       links:
diff --git a/articles/governance/service-groups/create-service-group-member-rest-api.md b/articles/governance/service-groups/create-service-group-member-rest-api.md
@@ -1,19 +1,21 @@
 ---
-title: Quickstart: Connect service group members with REST API
+title: "Quickstart: Connect Service Group members using the REST API"
 description: In this quickstart, you use REST API to connect a resource to a service group with a service group member relationship.
 author: rthorn17
 ms.author: rithorn
-ms.service: Azure Service Groups
-ms.topic: quickstart  #Don't change
+ms.service: azure-governance
+ms.topic: quickstart
 ms.date: 5/19/2025
 ---
 
 
 # Quickstart: Connect resources or resource containers to service groups with Service Group Member Relationships 
  
-Service Groups are designed to be flexible and scalable, allowing organizations to adapt their resource management strategies as their needs evolve. To connect resources, resource groups, or subscriptions to a Service Group, you need to create a new Service Group Member Relationship. For more information on service groups, see [Getting started with Service Groups](overview.md).
-
+To connect resources, resource groups, or subscriptions to a Service Group (preview), you need to create a new Service Group Member Relationship. For more information on service groups, see [Getting started with Service Groups](overview.md).
 
+> [!IMPORTANT]
+> Azure Service Groups is currently in PREVIEW. For more information about participating in the preview, see [TBD Link]().
+> 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.
 
 ## Prerequisites
 
@@ -26,9 +28,9 @@ Service Groups are designed to be flexible and scalable, allowing organizations
 ## Create in REST API
 
 For REST API, use the
-[Service Groups Member- Create or Update]() endpoint to create a new service group member. 
+[Service Groups Member- Create or Update]() endpoint to create a new service group member.
 
-In this example, we're connecting a Virtual Machine [VM1] to a Service Group [Contoso]. 
+In this example, we're connecting a Virtual Machine [VM1] to a Service Group [Contoso].
 
 1. Service Group: **groupId** is _Contoso_
 1. Virtual Machine: The **resourceID** is _VM1_
@@ -76,19 +78,13 @@ To remove the service group created in this document, use the
 - No Request Body
 
 
-## Next step -or- Related content
+## Next step
 
 In this quickstart, you created a service group to help create different views in Azure. The
 service group can have member subscriptions, resource groups, resources, or other service groups.
 
 To learn more about service groups and how to manage your service group hierarchy, continue to:
 
 > [!div class="nextstepaction"]
-> [Manage your resources with service groups]()
-
-
--or-
+> [Manage your resources with service groups](manaage-service-groups.md)
 
-- [Related article title](link.md)
-- [Related article title](link.md)
-- [Related article title](link.md)
diff --git a/articles/governance/service-groups/create-service-group-rest-api.md b/articles/governance/service-groups/create-service-group-rest-api.md
@@ -3,17 +3,19 @@ title: Quickstart: Create a service group with REST API
 description: In this quickstart, you use REST API to create a service group to organize your resources.
 author: rthorn17
 ms.author: rithorn
-ms.service: Azure Service Groups
-ms.topic: quickstart  #Don't change
+ms.service: azure-governance
+ms.topic: quickstart  
 ms.date: 5/19/2025
 ---
 
 
-# Quickstart: Create a service group with REST API
+# Quickstart: Create a service group (preview) with REST API
  
-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. Service Groups are designed to complement existing organizational structures like Resource Groups, Subscriptions, and Management Groups by offering a flexible and secure way to aggregate resources for specific purposes. For more information on service groups, see [Getting started with Service Groups](overview.md).
-
+With Azure Service Groups (preview) you can create low-privilege-based groupings 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. Service Groups are designed to complement existing organizational structures like Resource Groups, Subscriptions, and Management Groups by offering a flexible and secure way to aggregate resources for specific purposes. For more information on service groups, see [Getting started with Service Groups](overview.md).
 
+> [!IMPORTANT]
+> Azure Service Groups is currently in PREVIEW. For more information about participating in the preview, see [TBD Link]().
+> 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.
 
 ## Prerequisites
 
@@ -101,20 +103,7 @@ To remove the service group created in this document, use the
 
 - No Request Body
 
-
-## Next step -or- Related content
-
-In this quickstart, you created a service group to help create different views in Azure. The
-service group can have member subscriptions, resource groups, resources, or other service groups.
-
-To learn more about service groups and how to manage your service group hierarchy, continue to:
-
-> [!div class="nextstepaction"]
-> [Manage your resources with service groups]()
-
-
--or-
-
-- [Related article title](link.md)
-- [Related article title](link.md)
-- [Related article title](link.md)
+## Related content
+* [What are Azure Service Groups?](overview.md)
+* [How to: Manage Service Groups](manaage-service-groups.md)
+* [Connect service group members with REST API](create-service-group-member-rest-api.md)
diff --git a/articles/governance/service-groups/manage-service-groups.md b/articles/governance/service-groups/manage-service-groups.md
@@ -1,24 +1,22 @@
 ---
-title: Manage Azure Service Groups 
-description: "Learn how to create, update, read, and delete Azure Service Groups and its members"
+title: Manage resouces across subscriptions and resource groups with Azure Service Groups 
+description: "Learn how to create, update, read, and delete Azure Service Groups and members"
 author: rthorn17
 ms.author: rithorn
-ms.service: Service Groups
-ms.topic: overview #Don't change
+ms.service: azure-governance  ## is service-groups going to be an official service slug?
+ms.topic: how-to
 ms.date: 05/19/2025
 ---
 
-# How to manage Azure Service Groups?
+# How to use Azure Service Groups to manage resources
 
-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.  
+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.  
 
 For more information on service groups, see [Getting started with Service Groups](overview.md).
 
-> ![IMPORTANT]
-> Service Groups are currently in a Limited Preview state and require Tenant onboarding before trial. To request for onboarding please see [TBD Link](). 
->
-> 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.   
-
+> [!IMPORTANT]
+> Azure Service Groups is currently in PREVIEW. For more information about participating in the preview, see [TBD Link]().
+> 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.
 
 
 ## Service Group Actions
@@ -32,7 +30,7 @@ This section shows you how to manage service group's actions create, read, updat
 - API Version: **2024-04-01-preview**
 - URL: https://management.azure.com/providers/Microsoft.Management/serviceGroups/[groupID]?api-version=2024-04-01-preview
 
-Request Body: 
+Request Body:
 ```json
 {
     "kind":[kind],
@@ -192,9 +190,9 @@ Service group members are resources, resource groups, or subscriptions that are
 |------|-------------------------|--------------------------------|
 |Structure| Hierarchical|Flexible and dynamic|
 |Inheritance|Yes|No|
-|Scope|Service Group property|	Extends resources, resource groups, and subscriptions as its own resource|
-|Use Case|	Governance management |	Aggregating resources across different scopes |
-|Flexibility| Rigid/Strict (One Parent, Many Children) |	Flexible (Many Parents, Many Children)|
+|Scope|Service Group property| Extends resources, resource groups, and subscriptions as its own resource|
+|Use Case| Governance management | Aggregating resources across different scopes |
+|Flexibility| Rigid/Strict (One Parent, Many Children) | Flexible (Many Parents, Many Children)|
 
 ### Child/Parent Relationship Using the "Parent" Property
 
@@ -347,30 +345,8 @@ The valid values are:
 * UserExplicitlyCreated: A user created the relationship.
 
 
-
-  
-
-
-
-
-
-
 ## Related content
-
-- [Related article title](link.md)
-- [Related article title](link.md)
-- [Related article title](link.md)
-
-<!-- Optional: Related content - H2
-
-Consider including a "Related content" H2 section that 
-lists links to 1 to 3 articles the user might find helpful.
-
--->
-
-<!--
-
-Remove all comments except the customer intent
-before you sign off or merge to the main branch.
-
---> 
+* [What are Azure Service Groups?](overview.md)
+* [Quickstart: Create a service group (preview) with REST API](create-service-group-rest-api.md)
+* [Quickstart: Connect resources or resource containers to service groups with Service Group Member Relationships](create-service-group-member-rest-api.md)
+* [Connect service group members with REST API](create-service-group-member-rest-api.md)
diff --git a/articles/governance/service-groups/overview.md b/articles/governance/service-groups/overview.md
@@ -3,33 +3,43 @@ title: "Get started with Service Groups"
 description: "Learn how to use and manage resources with Service Groups."
 author: rthorn17
 ms.author: rithorn
-ms.service: Service Groups
-ms.topic: concept-article #Don't change
+ms.service: governance
+ms.topic: overview
 ms.date: 05/19/2025
 ---
 
 # What are Azure Service Groups?
 
 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. Service Groups are designed to complement existing organizational structures like Resource Groups, Subscriptions, and Management Groups by offering a flexible and secure way to aggregate resources for specific purposes. This article helps give you an overview of what Service Groups are, the scenarios to use them for, and provide guidance on how to get started. 
 
-> ![IMPORTANT]
-> Service Groups are currently in a Limited Preview state and require Tenant onboarding before trial. To request for onboarding please see [TBD Link](). 
+> [!IMPORTANT]
+> Service Groups is currently in PREVIEW. For more information about participating in the preview, see [TBD Link]().
+> 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.
 
 
 ## Key capabilities
-* **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. 
-* **Low Privilege Management**: Service Groups are designed to operate with minimal permissions, ensuring that users can manage resources without needing excessive access rights.
-* **Multiple Hierarchies**: Service Groups live outside of the resource hierarchy enabling scenarios where the same resources need to be group for different purposes.   
+- **Multiple Hierarchies**: Service Groups live outside of the resource hierarchy enabling scenarios where the same resources need to be group for different purposes.*
+- **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. 
+- **Low Privilege Management**: Service Groups are designed to operate with minimal permissions, ensuring that users can manage resources without needing excessive access rights.
 
 
+### Multiple Hierarchies 
+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.   
+
+#### Example Scenarios
+* Separate Personas 
+    * 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. 
+
+![MultipleSGTree](./media/MultiSG.png)
+
 ### Flexible Membership
-Within the Resource Hierarchy, 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.  
+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.  
 
 #### Example Scenarios 
 * Aggregating Health Metrics
    * Organizations with multiple applications and environments can use Service Groups to aggregate health 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 health metrics.
 * Creating Inventory of a specific resource type
-    * Customers can connect all Virtual Machines or CosmosDBs to the same Service Groups to get a consolidated view of all the resources of that type in the entire environment. This capability allows a customer like a Virtual Machine Administrator to view aggregated data on all their resources no matter what subscription they live in.  
+    * Customers can connect all Virtual Machines or CosmosDBs to the same Service Groups to get a consolidated view of all the resources of that type in the entire environment. This capability allows a customer like a Virtual Machine Administrator to view aggregated data on all their resources no matter what subscription they live in.
 
 ![MGsandSGs](./media/sidebyside.png)
 
@@ -40,14 +50,6 @@ Service Groups don't have the same inheritance capabilities that other Azure Res
 * Aggregating monitoring metrics 
    * 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. 
 
-### Multiple Hierarchies 
-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.   
-
-#### Example Scenarios
-* Separate Personas 
-    * 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. 
-
-![MultipleSGTree](./media/MultiSG.png)
 
 ## How it works
 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. 
@@ -97,15 +99,8 @@ Service Groups creates the Root Service Group on the first request received with
 Access to the root has to be given from a user with "microsoft.authorization/roleassignments/write" permissions at the tenant level. For example, the Tenant's Global Administrator can elevate their access on the tenant to have these permissions. [Details on elevating Tenant Global Administrator Accesses](https://learn.microsoft.com/en-us/azure/role-based-access-control/elevate-access-global-admin?tabs=azure-portal%2Centra-audit-logs)
 
 
-## Next step -or- Related content
-
-> [!div class="nextstepaction"]
-> [Getting Started: Service Groups](link.md)
-
--or-
+## Related content
+* [Quickstart: Create a service group with REST API](service-groups\create-service-group-rest-api.md)
+* [How to: Manage Service Groups](manaage-service-groups.md)
+* [Connect service group members with REST API](create-service-group-member-rest-api.md)
 
-* [How to: Connect Service Group Members](link.md)
-* [How to:](link.md)
-* [Related article title](link.md)
-* [Service Group REST API Spec]()
-* [Service Group Member REST API Spec]()
