Merge branch 'main' into doc-improvement-create-chat

Author: v-sdhakshina

api-reference/beta/api/application-post-calls.md

@@ -1430,6 +1430,42 @@ Content-Type: application/json
               "removedState": {
                 "reason": "Removed from roster"
               }
+            },
+            {
+              "@odata.type": "#microsoft.graph.participant",
+              "info": {
+                "@odata.type": "#microsoft.graph.participantInfo",
+                "identity": {
+                  "@odata.type": "#microsoft.graph.identitySet",
+                  "acsUser": {
+                    "@odata.type": "#microsoft.graph.identity",
+                    "id": "f56e36db-9bb3-4fca-b794-a3efd7361f09_00000022-175f-5180-3397-b23a0d0047e8",
+                    "identityProvider": "None",
+                    "acsResourceId": "f56e36db-9bb3-4fca-b794-a3efd7361f09"
+                  }
+                },
+                "endpointType": "default",
+                "endpointId": "99b83373-efe6-405f-ba33-32043e9de267",
+                "clientVersion": "Microsoft.Skype.Calling.Test.Ccts/1.19.4966.0",
+                "participantId": "62de48e1-a72c-40db-9193-a3bd8cf167c9"
+              },
+              "mediaStreams": [
+                {
+                  "@odata.type": "#microsoft.graph.mediaStream",
+                  "mediaType": "audio",
+                  "label": "main-audio",
+                  "sourceId": "402",
+                  "direction": "sendReceive",
+                  "serverMuted": false
+                }
+              ],
+              "isMuted": false,
+              "isOnHold": false,
+              "isInLobby": false,
+              "publishedStates": [],
+              "meetingRole": "none",
+              "isIdentityAnonymized": false,
+              "id": "62de48e1-a72c-40db-9193-a3bd8cf167c9"
             }
           ],
           "sequenceNumber": 1
@@ -1440,7 +1476,9 @@ Content-Type: application/json
 }
 ```
 
->**Note:** For join meeting scenarios apart from call state notifications, we receive roster notifications.
+> **Notes:** 
+> * For join meeting scenarios apart from call state notifications, we receive roster notifications. 
+> * During the roster notification, ACS identities are also provided and recognized as **acsUser** entries.
 
 ### Example 6: Join a scheduled meeting with joinMeetingId and passcode
 The following example  requires a **joinMeetingId** and a **passcode** to join an existing meeting. You can retrieve these properties from the [Get onlineMeeting](../api/onlinemeeting-get.md) API.
@@ -2349,6 +2387,42 @@ Content-Type: application/json
           "isMuted": false,
           "isInLobby": true,
           "id": "05491616-385f-44a8-9974-18cc5f9933c1"
+        },
+        {
+          "@odata.type": "#microsoft.graph.participant",
+          "info": {
+            "@odata.type": "#microsoft.graph.participantInfo",
+            "identity": {
+              "@odata.type": "#microsoft.graph.identitySet",
+              "acsUser": {
+                "@odata.type": "#microsoft.graph.identity",
+                "id": "f56e36db-9bb3-4fca-b794-a3efd7361f09_00000022-175f-5180-3397-b23a0d0047e8",
+                "identityProvider": "None",
+                "acsResourceId": "f56e36db-9bb3-4fca-b794-a3efd7361f09"
+              }
+            },
+            "endpointType": "default",
+            "endpointId": "99b83373-efe6-405f-ba33-32043e9de267",
+            "clientVersion": "Microsoft.Skype.Calling.Test.Ccts/1.19.4966.0",
+            "participantId": "62de48e1-a72c-40db-9193-a3bd8cf167c9"
+          },
+          "mediaStreams": [
+            {
+              "@odata.type": "#microsoft.graph.mediaStream",
+              "mediaType": "audio",
+              "label": "main-audio",
+              "sourceId": "402",
+              "direction": "sendReceive",
+              "serverMuted": false
+            }
+          ],
+          "isMuted": false,
+          "isOnHold": false,
+          "isInLobby": false,
+          "publishedStates": [],
+          "meetingRole": "none",
+          "isIdentityAnonymized": false,
+          "id": "62de48e1-a72c-40db-9193-a3bd8cf167c9"
         }
       ]
     }
@@ -2411,11 +2485,13 @@ Content-Type: application/json
 }
 ```
 
-> **Note:** The application doesn't receive the roster for participants in the meeting until its admitted from lobby.
+> **Notes:** 
+> * The application doesn't receive the roster for participants in the meeting until its admitted from lobby. 
+> * During the roster notification, ACS identities are also provided and recognized as **acsUser** entries.
 
 ### Example 11: Create peer-to-peer PSTN call with service hosted media
 
-> **Note:** This call requires the Calls.Initiate.All permission.
+> **Note:** This call requires the `Calls.Initiate.All` permission.
 
 This call requires an application instance with a PSTN number assigned. For details, see [Assign a phone number to your bot](/graph/cloud-communications-phone-number#assign-a-phone-number-to-your-bot).
 

api-reference/beta/api/onauthenticationmethodloadstartexternalusersselfservicesignup-post-identityproviders.md

@@ -41,7 +41,7 @@ POST /identity/authenticationEventsFlows/{authenticationEventsFlow-id}/microsoft
 |Content-Type|application/json. Required.|
 
 ## Request body
-In the request body, provide a JSON representation of the ID of the [identityProvider](../resources/identityproviderbase.md) you want to add. For self-service sign up user flows, the values can be `EmailPassword-OAUTH`, `EmailOtpSignup-OAUTH`, `Google-OAUTH` or `Facebook-OAUTH`.
+In the request body, provide a JSON representation of the ID of the [identityProvider](../resources/identityproviderbase.md) you want to add.
 
 ## Response
 

api-reference/beta/api/presence-setpresence.md

@@ -23,7 +23,7 @@ A user can have multiple presence sessions because the user can be on multiple T
 
 Similarly, an application can have its own presence session for a user and be able to update the state.
 
-The following is the precedence for how session states are aggregated, with "A > B" representing A having precedence over B:
+The following precedence is used for how session states are aggregated, with "A > B" representing that A has precedence over B:
 * User-preferred state > session-level states (user-preferred state overrides session-level states)
 * Among session-level states: DoNotDisturb > Busy > Available > Away
 
@@ -34,7 +34,7 @@ A presence session may **time out** and **expire**, so the application needs to
 
 A presence session can time out if the availability is `Available` and the timeout is 5 minutes. When it times out, the presence state fades in stages. For example, if an application sets the presence session as `Available/Available`, the state would change to `Available/AvailableInactive` in 5 minutes with the first timeout, then `Away/Away` in another 5 minutes with the second timeout.
 
-The expiration of a presence session is configurable with the `expirationDuration` parameter. When a session expires it becomes `Offline`.
+Use `expirationDuration` to configure the expiration of a presence session; otherwise, the default expiration is 5 minutes. Valid values range from 5 minutes to 4 hours, after which the session becomes `Offline`.
 
 ## 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).
@@ -62,7 +62,7 @@ In the request body, provide a JSON object with the following parameters.
 | sessionId          | string   | The ID of the application's presence session.                                                          |
 | availability       | string   | The base presence information.                                                                         |
 | activity           | string   | The supplemental information to availability.                                                          |
-| expirationDuration | duration | The expiration of the app presence session. The value is represented in [ISO 8601 format for durations](http://en.wikipedia.org/wiki/ISO_8601#Durations).</p>If not provided, a default expiration of 5 minutes will be applied. |
+| expirationDuration | duration | The expiration of the app presence session. The value is represented in [ISO 8601 format for durations](http://en.wikipedia.org/wiki/ISO_8601#Durations).</p> If not provided, a default expiration of 5 minutes is applied. The valid duration range is from 5 to 240 minutes (PT5M to PT4H). |
 
 > [!IMPORTANT]
 >

api-reference/beta/resources/cloudpcreports.md

@@ -27,9 +27,9 @@ Use a method in the [Methods](#methods) section to get the corresponding report
 |[Get frontline report](../api/cloudpcreports-getfrontlinereport.md)|Stream| Get Frontline Cloud PC license usage reports, such as **servicePlanId**, **licenseCount**, and **claimedLicenseCount**, for real-time, 7 days, or 28 days trend.|
 |[Get inaccessible Cloud PC reports](../api/cloudpcreports-getinaccessiblecloudpcreports.md)|Stream|Get inaccessible Cloud PCs with details, including the latest health state, failed connection count, failed health check count, and system status.|
 |[Get raw remote connection reports](../api/cloudpcreports-getrawremoteconnectionreports.md)|Stream|Get the raw real-time remote connection report for a Cloud PC without any calculation or aggregation.|
-|[Get real time remote connection agency reports](../api/cloudpcreports-getrealtimeremoteconnectionlatency.md)|Stream|Get the real-time remote connection latency reports like current round trip time and available bandwidth of a Cloud PC.|
+|[Get real-time remote connection latency reports](../api/cloudpcreports-getrealtimeremoteconnectionlatency.md)|Stream|Get the real-time remote connection latency reports like current round trip time and available bandwidth of a Cloud PC.|
 |[Get real-time remote connection status reports](../api/cloudpcreports-getrealtimeremoteconnectionstatus.md)|Stream|Get the real-time remote connection status reports like sign-in status or days since the last use of a Cloud PC.|
-|[Get remove connection hitorical reports](../api/cloudpcreports-getremoteconnectionhistoricalreports.md)|Stream|Get a Cloud PC's remote connection historical reports, such as **signInDateTime**, **signOutDateTime**, or **usageInHour**, in a given period.|
+|[Get remote connection historical reports](../api/cloudpcreports-getremoteconnectionhistoricalreports.md)|Stream|Get a Cloud PC's remote connection historical reports, such as **signInDateTime**, **signOutDateTime**, or **usageInHour**, in a given period.|
 |[Get total aggregated remote connection reports](../api/cloudpcreports-gettotalaggregatedremoteconnectionreports.md)|Stream|Get the total aggregated remote connection reports, like usage and **daysSinceLastUse**, in a given period.|
 |[Retrieve Cloud PC tenant metrics report](../api/cloudpcreports-retrievecloudpctenantmetricsreport.md)|Stream|Get a report related to the performance of Cloud PCs.|
 |[Retrieve cross-region disaster recovery report](../api/cloudpcreports-retrievecrossregiondisasterrecoveryreport.md)|Stream| Retrieve the Windows 365 cross-region disaster recovery report with configuration health check results, disaster recovery status, latest cross-region restore points, and user settings.|
@@ -40,6 +40,7 @@ Use a method in the [Methods](#methods) section to get the corresponding report
 |[Get shared use license usage report (deprecated)](../api/cloudpcreports-getshareduselicenseusagereport.md) |Stream| Get the shared use license usage reports, such as **servicePlanId**, **licenseCount**, and **claimedLicenseCount**, for real-time, 7 days, or 28 days trend.|
 
 ## Properties
+
 |Property|Type|Description|
 |:---|:---|:---|
 |id|String|The unique identifier for the reports. Read-only. |
@@ -53,11 +54,13 @@ Use a method in the [Methods](#methods) section to get the corresponding report
 | cloudPcInsightReport       | Indicates Cloud PC-level configuration data with insights.   |
 
 ## Relationships
+
 |Relationship|Type|Description|
 |:---|:---|:---|
 |exportJobs|[cloudPcExportJob](../resources/cloudpcexportjob.md) collection|The export jobs created for downloading reports.|
 
 ## JSON representation
+
 The following JSON representation shows the resource type.
 <!-- {
   "blockType": "resource",

api-reference/beta/toc/device-and-app-management/toc.yml

@@ -286,11 +286,11 @@ items:
       href: ../../api/cloudpcreports-getinaccessiblecloudpcreports.md
     - name: Get raw remote connection reports
       href: ../../api/cloudpcreports-getrawremoteconnectionreports.md
-    - name: Get real time remote connection agency reports
+    - name: Get real-time remote connection latency reports
       href: ../../api/cloudpcreports-getrealtimeremoteconnectionlatency.md
     - name: Get real-time remote connection status reports
       href: ../../api/cloudpcreports-getrealtimeremoteconnectionstatus.md
-    - name: Get remove connection hitorical reports
+    - name: Get remote connection historical reports
       href: ../../api/cloudpcreports-getremoteconnectionhistoricalreports.md
     - name: Get total aggregated remote connection reports
       href: ../../api/cloudpcreports-gettotalaggregatedremoteconnectionreports.md

api-reference/v1.0/api/onauthenticationmethodloadstartexternalusersselfservicesignup-post-identityproviders.md

@@ -39,7 +39,7 @@ POST /identity/authenticationEventsFlows/{authenticationEventsFlow-id}/microsoft
 |Content-Type|application/json. Required.|
 
 ## Request body
-In the request body, provide a JSON representation of the ID of the [identityProvider](../resources/identityproviderbase.md) you want to add. For self-service user flows, the values can be `EmailPassword-OAUTH`, `EmailOtpSignup-OAUTH`, `Google-OAUTH`, or `Facebook-OAUTH`.
+In the request body, provide a JSON representation of the ID of the [identityProvider](../resources/identityproviderbase.md) you want to add. For self-service sign up user flows, the values can be `EmailPassword-OAUTH`, `EmailOtpSignup-OAUTH`, `Google-OAUTH` or `Facebook-OAUTH`.
 
 ## Response
 

api-reference/v1.0/api/presence-setpresence.md

@@ -21,7 +21,7 @@ A user can have multiple presence sessions because the user can be on multiple T
 
 Similarly, an application can have its own presence session for a user and be able to update the state.
 
-The following is the precedence for how session states are aggregated:
+The following precedence is used for how session states are aggregated:
 * User-configured > app-configured (user-configured state overrides others)
 * Among app-configured: DoNotDisturb > Busy > Available > Away
 
@@ -32,7 +32,7 @@ A presence session may **time out** and **expire**, so the application needs to
 
 A presence session can time out if the availability is `Available` and the timeout is 5 minutes. When it times out, the presence state fades in stages. For example, if an application sets the presence session as `Available/Available`, the state would change to `Available/AvailableInactive` in 5 minutes with the first timeout, then `Away/Away` in another 5 minutes with the second timeout.
 
-The expiration of a presence session is configurable with the `expirationDuration` parameter. When a session expires it becomes `Offline`.
+Use `expirationDuration` to configure the expiration of a presence session; otherwise, the default expiration is 5 minutes. Valid values range from 5 minutes to 4 hours, after which the session becomes `Offline`.
 
 ## 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).
@@ -60,7 +60,7 @@ In the request body, provide a JSON object with the following parameters.
 | sessionId          | string   | The ID of the application's presence session.                                                          |
 | availability       | string   | The base presence information.                                                                         |
 | activity           | string   | The supplemental information to availability.                                                          |
-| expirationDuration | duration | The expiration of the app presence session. The value is represented in [ISO 8601 format for durations](http://en.wikipedia.org/wiki/ISO_8601#Durations).</p>If not provided, a default expiration of 5 minutes will be applied. The valid duration range is 5-240 minutes (PT5M to PT4H)|
+| expirationDuration | duration | The expiration of the app presence session. The value is represented in [ISO 8601 format for durations](http://en.wikipedia.org/wiki/ISO_8601#Durations).</p>If not provided, a default expiration of 5 minutes is applied. The valid duration range is from 5 to 240 minutes (PT5M to PT4H).|
 
 > [!IMPORTANT]
 >