Merge pull request #26205 from microsoftgraph/fixUUF-groupMembers

Fix UUF - correct group-post-members.md syntax + examples

Author: FaithOmbongi

api-reference/beta/api/group-post-members.md

@@ -55,7 +55,7 @@ The following table shows the least privileged permission that's required by eac
 
 ```http
 POST /groups/{group-id}/members/$ref
-POST /groups/{group-id}/members/
+PATCH /groups/{group-id}/members
 ```
 
 ## Request headers
@@ -67,11 +67,16 @@ POST /groups/{group-id}/members/
 
 ## Request body
 
-When using the `/groups/{group-id}/members/$ref` syntax, supply a JSON object that contains an **@odata.id** property with a reference by ID to a supported group member object type.
+When using the `POST /groups/{group-id}/members/$ref` syntax, supply a JSON object that contains an **@odata.id** property with a reference by ID to a supported group member object type.
 
-When using the `/groups/{group-id}/members` syntax, supply a JSON object that contains a **members@odata.bind** property with one or more references by IDs to a supported group member object type.
-
-If using the **directoryObjects** reference, that is, `https://graph.microsoft.com/v1.0/directoryObjects/{id}`, the object type must still be a supported group member object type.
+When using the `PATCH /groups/{group-id}/members` syntax, supply a JSON object that contains a **members@odata.bind** property with one or more references by IDs to a supported group member object type. That is:
+- For Microsoft 365 groups, only `https://graph.microsoft.com/v1.0/directoryObjects/{id}` and `https://graph.microsoft.com/v1.0/groups/{id}` is allowed where `{id}` must be a user because only users can members of Microsoft 365 groups.
+- For security groups, the following ID references are allowed:
+  - `https://graph.microsoft.com/v1.0/directoryObjects/{id}` where `{id}` must belong to a user, security group, device, service principal, or organizational contact.
+  - `https://graph.microsoft.com/v1.0/groups/{id}` where `{id}` must belong to another security group. Microsoft 365 groups can't be members of security groups.
+  - `https://graph.microsoft.com/v1.0/devices/{id}` where `{id}` belongs to a device.
+  - `https://graph.microsoft.com/v1.0/servicePrincipal/{id}` where `{id}` belongs to a service principal.
+  - `https://graph.microsoft.com/v1.0/orgContact/{id}` where `{id}` belongs to an organizational contact.
 
 ## Response
 
@@ -82,9 +87,11 @@ If successful, this method returns a `204 No Content` response code. It returns
 
 ## Example
 
-### Request
+### Example 1: Add a member to a group
 
-The following example shows a request.
+#### Request
+
+The following example shows a request that uses the **directoryObjects** reference to add a member to a group.
 
 # [HTTP](#tab/http)
 
@@ -136,9 +143,44 @@ Content-type: application/json
 
 ---
 
-In the request body, supply a JSON representation of the `id` of the [directoryObject](../resources/directoryobject.md), [user](../resources/user.md), or [group](../resources/group.md) object you want to add.
+#### Response
+
+The following example shows the response.
+
+<!-- {
+  "blockType": "response"
+} -->
+
+```http
+HTTP/1.1 204 No Content
+```
+
+### Example 2: Add multiple members to a group in a single request
+
+This example shows how to add multiple members to a group with OData bind support in a PATCH operation. Up to 20 members can be added in a single request. If an error condition exists in the request body, no members are added and the appropriate response code is returned.
+
+#### Request
+
+The following example shows a request.
+<!-- {
+  "blockType": "request",
+  "name": "add_multiple_members_to_group"
+}-->
+
+```http
+PATCH https://graph.microsoft.com/beta/groups/{group-id}
+Content-type: application/json
+
+{
+  "members@odata.bind": [
+    "https://graph.microsoft.com/beta/directoryObjects/{id}",
+    "https://graph.microsoft.com/beta/directoryObjects/{id}",
+    "https://graph.microsoft.com/beta/directoryObjects/{id}"
+    ]
+}
+```
 
-### Response
+#### Response
 
 The following example shows the response.
 

api-reference/v1.0/api/group-post-members.md

@@ -53,7 +53,7 @@ The following table shows the least privileged permission that's required by eac
 
 ```http
 POST /groups/{group-id}/members/$ref
-POST /groups/{group-id}/members/
+PATCH /groups/{group-id}/members
 ```
 
 ## Request headers
@@ -65,11 +65,16 @@ POST /groups/{group-id}/members/
 
 ## Request body
 
-When using the `/groups/{group-id}/members/$ref` syntax, supply a JSON object that contains an **@odata.id** property with a reference by ID to a supported group member object type.
+When using the `POST /groups/{group-id}/members/$ref` syntax, supply a JSON object that contains an **@odata.id** property with a reference by ID to a supported group member object type.
 
-When using the `/groups/{group-id}/members` syntax, supply a JSON object that contains a **members@odata.bind** property with one or more references by IDs to a supported group member object type.
-
-If using the **directoryObjects** reference, that is, `https://graph.microsoft.com/v1.0/directoryObjects/{id}`, the object type must still be a supported group member object type.
+When using the `PATCH /groups/{group-id}/members` syntax, supply a JSON object that contains a **members@odata.bind** property with one or more references by IDs to a supported group member object type. That is:
+- For Microsoft 365 groups, only `https://graph.microsoft.com/v1.0/directoryObjects/{id}` and `https://graph.microsoft.com/v1.0/groups/{id}` is allowed where `{id}` must be a user because only users can members of Microsoft 365 groups.
+- For security groups, the following ID references are allowed:
+  - `https://graph.microsoft.com/v1.0/directoryObjects/{id}` where `{id}` must belong to a user, security group, device, service principal, or organizational contact.
+  - `https://graph.microsoft.com/v1.0/groups/{id}` where `{id}` must belong to another security group. Microsoft 365 groups can't be members of security groups.
+  - `https://graph.microsoft.com/v1.0/devices/{id}` where `{id}` belongs to a device.
+  - `https://graph.microsoft.com/v1.0/servicePrincipal/{id}` where `{id}` belongs to a service principal.
+  - `https://graph.microsoft.com/v1.0/orgContact/{id}` where `{id}` belongs to an organizational contact.
 
 ## Response
 
@@ -136,8 +141,6 @@ Content-type: application/json
 
 ---
 
-In the request body, supply a JSON representation of the id of the directoryObject, user, or group object you want to add.
-
 #### Response
 
 The following example shows the response.
@@ -152,7 +155,7 @@ HTTP/1.1 204 No Content
 
 ### Example 2: Add multiple members to a group in a single request
 
-This example shows how to add multiple members to a group with OData bind support in a PATCH operation. Up to 20 members can be added in a single request. The POST operation isn't supported. If an error condition exists in the request body, no members are added and the appropriate response code is returned.
+This example shows how to add multiple members to a group with OData bind support in a PATCH operation. Up to 20 members can be added in a single request. If an error condition exists in the request body, no members are added and the appropriate response code is returned.
 
 #### Request