Merge pull request #25836 from microsoftgraph/mwahl-em-rr-noid

entitlement management: adding group member/owner as resource role, clarify roles and id

Author: Lauragra

api-reference/v1.0/api/accesspackage-post-resourcerolescopes.md

@@ -42,7 +42,7 @@ POST /identityGovernance/entitlementManagement/accessPackages/{id}/resourceRoleS
 
 ## Request body
 
-In the request body, supply a JSON representation of an [accessPackageResourceRoleScope](../resources/accesspackageresourcerolescope.md) object.  Include in the object the relationships to an [accessPackageResourceRole](../resources/accesspackageresourcerole.md) object and an [accessPackageResourceScope](../resources/accesspackageresourcescope.md) object, which can be obtained from a request to [list access package resources a catalog](accesspackagecatalog-list-resourceroles.md), with `$expand=roles,scopes`.
+In the request body, supply a JSON representation of an [accessPackageResourceRoleScope](../resources/accesspackageresourcerolescope.md) object. Include in the object the relationships to an [accessPackageResourceRole](../resources/accesspackageresourcerole.md) object and an [accessPackageResourceScope](../resources/accesspackageresourcescope.md) object, which can be obtained from a request to [list access package resources a catalog](accesspackagecatalog-list-resourceroles.md), with `$expand=roles,scopes`.
 
 ## Response
 
@@ -54,9 +54,9 @@ If successful, this method returns a 200-series response code and a new [accessP
 
 #### Request
 
-The following example shows a request adding a SharePoint Online site role to an access package's list of resource roles.  The access package resource for the site must already have been added to the access package catalog containing this access package.
+The following example shows a request adding a SharePoint Online site role to an access package's list of resource roles. The access package resource for the site must already have been added to the access package catalog containing this access package.
 
-The request contains an [accessPackageResourceRole](../resources/accesspackageresourcerole.md) object. Each type of resource defines the format of the originId field in a resource role. For a SharePoint Online site, the originId will be the sequence number of the role in the site.  The resource role can be obtained from a request to [retrieve the roles of a resource for a SharePoint Online site collection](accesspackagecatalog-list-resourceroles.md#example-2-retrieving-the-roles-of-a-resource-for-a-sharepoint-online-site-collection).
+The request contains an [accessPackageResourceRole](../resources/accesspackageresourcerole.md) object. Each type of resource defines the format of the originId field in a resource role. For a SharePoint Online site, the originId will be the sequence number of the role in the site. The resource role can be obtained from a request to [retrieve the roles of a resource for a SharePoint Online site collection](accesspackagecatalog-list-resourceroles.md#example-2-retrieving-the-roles-of-a-resource-for-a-sharepoint-online-site-collection).
 
 # [HTTP](#tab/http)
 <!-- {
@@ -148,7 +148,7 @@ Content-type: application/json
 
 #### Request
 
-The following example shows a request adding an application's role to an access package's list of resource roles.  The access package resource for the application must already have been added to the access package catalog containing this access package. The `role`, `resource` and `scope` can be obtained by a [list of the resources of a catalog](accesspackagecatalog-list-resources.md).
+The following example shows a request that adds an application's role to an access package's list of resource roles. The access package resource for the application must already be added to the access package catalog that contains this access package. You can get the `role`, `resource`, and `scope` with the [list resources](accesspackagecatalog-list-resources.md) method.
 
 # [HTTP](#tab/http)
 <!-- {
@@ -242,7 +242,7 @@ Content-type: application/json
 
 #### Request
 
-The following example shows a request adding membership of a group to an access package's list of resource roles.  The access package resource for the group must already have been added to the access package catalog containing this access package.  The `role`, `resource` and `scope` can be obtained by a [list of the resources of a catalog](accesspackagecatalog-list-resources.md).
+The following example shows a request that adds membership of a group to an access package's list of resource roles. The access package resource for the group must already be added to the access package catalog that contains this access package. You can get the `resource` and `scope` with the [list of the resources of a catalog](accesspackagecatalog-list-resources.md) method. You can get the `role` with the [list of the roles of the resource in the catalog](accesspackagecatalog-list-resourceroles.md) method. If the `role` returned from the list of the roles has a zero ID, then don't include an `id` in the `accessPackageResourceRole`.
 
 # [HTTP](#tab/http)
 <!-- {
@@ -256,7 +256,6 @@ Content-type: application/json
 
 {
     "role": {
-        "id": "748f8431-c7c6-404d-8564-df67aa8cfc5e",
         "displayName": "Member",
         "originSystem": "AadGroup",
         "originId": "Member_0282e19d-bf41-435d-92a4-99bab93af305",