Merge pull request #28702 from microsoftgraph/main

Merge to publish

Author: Danipocket

api-reference/beta/api/approvedclientapp-update.md

@@ -16,6 +16,8 @@ Namespace: microsoft.graph
 
 Update the properties of an [approvedClientApp](../resources/approvedclientapp.md) object for a [remotedesktopsecurityconfiguration](../resources/remotedesktopsecurityconfiguration.md).
 
+[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
+
 ## Permissions
 
 Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).

api-reference/beta/api/channel-list.md

@@ -61,7 +61,9 @@ Don't supply a request body for this method.
 
 ## Response
 
-If successful, this method returns a `200 OK` response code and collection of [Channel](../resources/channel.md) objects in the response body.
+If successful, this method returns a `200 OK` response code and a collection of [channel](../resources/channel.md) objects in the response body. 
+
+When the result set spans multiple pages, the response includes an **@odata.nextLink** property with a URL for retrieving the next page of results. For details about how to page through results, see [Paging Microsoft Graph data in your app](/graph/paging).
 
 ## Examples
 
@@ -145,7 +147,7 @@ Content-type: application/json
 ```
 
 > [!NOTE]
-> This API has a [known issue](https://microsoftgraph.visualstudio.com/Known%20Issues/_workitems/edit/40502/) related to listing channels. The **layoutType** property returns `null` when listing channels. To get the layout type of a specific channel, use the [Get channel](../api/channel-get.md) API. Full support for **layoutType** in list operations is planned for a future release.
+> This API has a [known issue](/graph/known-issues#layouttype-property-returns-null-when-listing-all-channels) related to listing channels. The **layoutType** property returns `null` when listing channels. To get the layout type of a specific channel, use the [Get channel](../api/channel-get.md) API.
 
 ### Example 2: List all private channels
 

api-reference/beta/api/channel-patch.md

@@ -165,13 +165,13 @@ HTTP/1.1 204 No Content
 }
 -->
 
-### Example 4: Update a channel's layout type
+### Example 4: Update the layout type of a channel
 
-This example shows how to update an existing channel's layout type from post to chat.
+The following example shows how to update the existing layout type of a channel from post to chat.
 
 #### Request
 
-The following example shows a request to change a channel's layout from the traditional post-reply format to a chat-like threading experience.
+The following example shows a request to change the layout of a channel from the traditional post-reply format to a chat-like threading experience.
 
 # [HTTP](#tab/http)
 <!-- {
@@ -232,10 +232,10 @@ HTTP/1.1 204 No Content
 
 ### Example 5: Switch a channel back to post layout type
 
-This example shows how to convert a chat-layout channel back to the traditional post-reply format.
+The following example shows how to convert a chat-layout channel back to the traditional post-reply format.
 
 #### Request
-
+The following example shows a request.
 # [HTTP](#tab/http)
 <!-- {
   "blockType": "request",

api-reference/beta/api/channel-post.md

@@ -241,11 +241,11 @@ Content-type: application/json
 
 ### Example 3: Create a channel with chat layout type
 
-This example shows how to create a channel with the chat layout type, which provides a chat-like threading experience similar to group chats.
+The following example shows how to create a channel with the chat layout type that provides a chat-like threading experience similar to group chats.
 
 #### Request
 
-The following example shows a request to create a channel with `layoutType` set to `chat`.
+The following example shows a request to create a channel with **layoutType** set to `chat`.
 
 # [HTTP](#tab/http)
 <!-- {

api-reference/beta/api/remotedesktopsecurityconfiguration-delete-approvedclientapps.md

@@ -15,6 +15,8 @@ Namespace: microsoft.graph
 
 Delete a [approvedClientApp](../resources/approvedclientapp.md) object for the [remoteDesktopSecurityConfiguration](../resources/remotedesktopsecurityconfiguration.md) object on a service principal.
 
+[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
+
 ## Permissions
 Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
 

api-reference/beta/api/remotedesktopsecurityconfiguration-list-approvedclientapps.md

@@ -14,6 +14,7 @@ Namespace: microsoft.graph
 [!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
 
 Get a list of the [approvedClientApp](../resources/approvedclientapp.md) objects and their properties on the [remoteDesktopSecurityConfiguration](../resources/remotedesktopsecurityconfiguration.md) resource on a service principal.
+
 [!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
 
 ## Permissions

api-reference/beta/api/remotedesktopsecurityconfiguration-post-approvedclientapps.md

@@ -15,6 +15,8 @@ Namespace: microsoft.graph
 
 Create a new [approvedClientApp](../resources/approvedclientapp.md) object for the [remoteDesktopSecurityConfiguration](../resources/remotedesktopsecurityconfiguration.md) object on a service principal. You can configure a maximum of 20 approved client apps.
 
+[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
+
 ## Permissions
 Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
 

api-reference/beta/api/serviceprincipal-list-remotedesktopsecurityconfiguration.md

@@ -16,6 +16,8 @@ Namespace: microsoft.graph
 
 Get a list of the [remoteDesktopSecurityConfiguration](../resources/remotedesktopsecurityconfiguration.md) objects and their properties.
 
+[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
+
 ## Permissions
 
 Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).

api-reference/beta/api/targetdevicegroup-get.md

@@ -15,6 +15,8 @@ Namespace: microsoft.graph
 
 Read the properties and relationships of a [targetDeviceGroup](../resources/targetdevicegroup.md) object for the remoteDesktopSecurityConfiguration object on the servicePrincipal.
 
+[!INCLUDE [national-cloud-support](../../includes/all-clouds.md)]
+
 ## Permissions
 Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions [only if your app requires it](/graph/permissions-overview#best-practices-for-using-microsoft-graph-permissions). For details about delegated and application permissions, see [Permission types](/graph/permissions-overview#permission-types). To learn more about these permissions, see the [permissions reference](/graph/permissions-reference).
 

api-reference/beta/api/team-list-allchannels.md

@@ -54,7 +54,9 @@ Don't supply a request body for this method.
 
 ## Response
 
-If successful, this method returns a `200 OK` response code and a collection of [channel](../resources/channel.md) objects in the response body. The response also includes the **@odata.id** property, which can be used to access the channel and run other operations on the [channel](../resources/channel.md) object.
+If successful, this method returns a `200 OK` response code and a collection of [channel](../resources/channel.md) objects in the response body. The response also includes the **@odata.id** property, which can be used to access the channel and run other operations on the [channel](../resources/channel.md) object. 
+
+When the result set spans multiple pages, the response includes an **@odata.nextLink** property with a URL for retrieving the next page of results. For details about how to page through results, see [Paging Microsoft Graph data in your app](/graph/paging).
 
 > [!Note]
 > Currently, invoking the URL returned from the **@odata.id** property fails for cross-tenant shared channels. You can solve this issue if you remove the `/tenants/{tenant-id}` part from the URL before you call this API. For more information, see [Known issues with Microsoft Graph](/graph/known-issues#unable-to-access-a-cross-tenant-shared-channel-when-the-request-url-contains-tenantscross-tenant-id).