Merge pull request #28204 from microsoftgraph/reezaali-addClientRequestIdHeader

Added client-request-id header information

Author: Danipocket

api-reference/beta/api/tenantdatasecurityandgovernance-processcontentasync.md

@@ -2,8 +2,8 @@
 title: "tenantDataSecurityAndGovernance: processContentAsync"
 toc.title: "tenantDataSecurityAndGovernance: processContentAsync"
 description: "Process a batch of tenant-wide content entries asynchronously against data protection policies."
-author: "ArunGedela"
-ms.date: 04/08/2025
+author: "reezaali149"
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -38,6 +38,7 @@ POST /security/dataSecurityAndGovernance/processContentAsync
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 

api-reference/beta/api/tenantprotectionscopecontainer-compute.md

@@ -3,7 +3,7 @@ title: "tenantProtectionScopeContainer: compute"
 toc.title: "tenantProtectionScopeContainer: compute"
 description: "Compute the tenant-wide data protection policies and actions, including user or group scoping."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -38,6 +38,7 @@ POST /security/dataSecurityAndGovernance/protectionScopes/compute
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 

api-reference/beta/api/userdatasecurityandgovernance-processcontent.md

@@ -3,7 +3,7 @@ title: "userDataSecurityAndGovernance: processContent"
 toc.title: "userDataSecurityAndGovernance: processContent"
 description: "Process content against data protection policies in the context of the current, or specified, user."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -47,6 +47,7 @@ POST /users/{userId}/dataSecurityAndGovernance/processContent
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 |Content-Type|application/json. Required.|
 | If-None-Match | Optional. This value is used by the API to determine if the policy state changed since the last call to the API. The value is from the Etag header returned from [protectionScopes compute](../api/userprotectionscopecontainer-compute.md). If newly computed Etag value does not match the value passsed in this header, protectionScopeState property returned will be "modified" and the app needs to refresh by calling [protectionScopes compute](../api/userprotectionscopecontainer-compute.md). |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 
@@ -84,6 +85,7 @@ The following example shows a request.
 ```http
 POST https://graph.microsoft.com/beta/me/dataSecurityAndGovernance/processContent
 Content-Type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
     "contentToProcess": {
@@ -170,6 +172,7 @@ The following example shows the response.
 ```http
 HTTP/1.1 200 OK
 Content-Type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
   "@odata.context": "https://graph.microsoft.com/beta/$metadata#microsoft.graph.processContentResponse",

api-reference/beta/api/userprotectionscopecontainer-compute.md

@@ -3,7 +3,7 @@ title: "userProtectionScopeContainer: compute"
 toc.title: "userProtectionScopeContainer: compute"
 description: "Compute the data protection policies and actions applicable to a specific user based on their context."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -46,7 +46,8 @@ POST /users/{usersId}/dataSecurityAndGovernance/protectionScopes/compute
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
-| If-None-Match | Optional. This value is used by the API to determine if the policy state has changed since the last call to the API. |
+| If-None-Match | Optional. This value is used by the API to determine if the policy state changed since the last call to the API. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID isn't provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request is returned in the response. |
 
 ## Request body
 
@@ -64,7 +65,7 @@ In the request body, provide a JSON object with the following parameters.
 
 | Name          | Description   |
 | :------------ | :------------ |
-| ETag          | An indicator whether the admin-configured policy state has changed. If the Etag matches the If-None-Match value and you have cached the results of parsing previous results from this API, there is no need to parse the response and cache the parsed results. Cache this value for calls to [process content](../api/userdatasecurityandgovernance-processcontent.md). |
+| ETag          | An indicator whether the admin-configured policy state changed. If the Etag matches the If-None-Match value and you cached the results of parsing previous results from this API, there's no need to parse the response and cache the parsed results. Cache this value for calls to [process content](../api/userdatasecurityandgovernance-processcontent.md). |
 
 ## Response
 
@@ -79,6 +80,7 @@ The following example computes the protection scope for a user performing text u
 ```http
 POST https://graph.microsoft.com/beta/users/7c1f8f10-cba8-4a8d-9449-db4b876d1ef70/dataSecurityAndGovernance/protectionScopes/compute
 Content-type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
    "activities": "uploadText,downloadText",
@@ -100,6 +102,7 @@ The following example shows the response. It indicates that for the `uploadText`
 ```http
 HTTP/1.1 200 OK
 Content-type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
   "@odata.context": "https://graph.microsoft.com/beta/$metadata#Collection(microsoft.graph.policyUserScope)",

api-reference/v1.0/api/tenantdatasecurityandgovernance-processcontentasync.md

@@ -3,7 +3,7 @@ title: "tenantDataSecurityAndGovernance: processContentAsync"
 toc.title: "tenantDataSecurityAndGovernance: processContentAsync"
 description: "Process a batch of tenant-wide content entries asynchronously against data protection policies."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -36,6 +36,7 @@ POST /security/dataSecurityAndGovernance/processContentAsync
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 

api-reference/v1.0/api/tenantprotectionscopecontainer-compute.md

@@ -3,7 +3,7 @@ title: "tenantProtectionScopeContainer: compute"
 toc.title: "tenantProtectionScopeContainer: compute"
 description: "Compute the tenant-wide data protection policies and actions, including user or group scoping."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -36,6 +36,7 @@ POST /security/dataSecurityAndGovernance/protectionScopes/compute
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 

api-reference/v1.0/api/userdatasecurityandgovernance-processcontent.md

@@ -3,7 +3,7 @@ title: "userDataSecurityAndGovernance: processContent"
 toc.title: "userDataSecurityAndGovernance: processContent"
 description: "Process content against data protection policies in the context of the current, or specified, user."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -45,6 +45,7 @@ POST /users/{userId}/dataSecurityAndGovernance/processContent
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 |Content-Type|application/json. Required.|
 | If-None-Match | Optional. This value is used by the API to determine if the policy state changed since the last call to the API. The value is from the Etag header returned from [protectionScopes compute](../api/userprotectionscopecontainer-compute.md). If newly computed Etag value does not match the value passsed in this header, protectionScopeState property returned will be "modified" and the app needs to refresh by calling [protectionScopes compute](../api/userprotectionscopecontainer-compute.md). |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID is not provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request will be returned in the response. |
 
 ## Request body
 
@@ -82,6 +83,7 @@ The following example shows a request.
 ```http
 POST https://graph.microsoft.com/v1.0/me/dataSecurityAndGovernance/processContent
 Content-Type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
     "contentToProcess": {
@@ -167,6 +169,7 @@ The following example shows the response.
 ```http
 HTTP/1.1 200 OK
 Content-Type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
   "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#microsoft.graph.processContentResponse",

api-reference/v1.0/api/userprotectionscopecontainer-compute.md

@@ -3,7 +3,7 @@ title: "userProtectionScopeContainer: compute"
 toc.title: "userProtectionScopeContainer: compute"
 description: "Compute the data protection policies and actions applicable to a specific user based on their context."
 author: "kylemar"
-ms.date: 06/19/2025
+ms.date: 02/06/2026
 ms.localizationpriority: medium
 ms.subservice: "security"
 doc_type: apiPageType
@@ -44,6 +44,7 @@ POST /users/{usersId}/dataSecurityAndGovernance/protectionScopes/compute
 | :------------ | :------------ |
 |Authorization|Bearer {token}. Required. Learn more about [authentication and authorization](/graph/auth/auth-concepts).|
 | Content-Type  | application/json. Required. |
+| Client-Request-Id  | String (GUID recommended). Optional. Unique identifier for this request, which is used for tracing and debugging in logs and support interactions. If an ID isn't provided, one may be generated automatically. We recommend that you specify the ID to make tracing and debugging easier. The same ID that was sent in the request is returned in the response. |
 
 ## Request body
 
@@ -61,7 +62,7 @@ In the request body, provide a JSON object with the following parameters.
 
 | Name          | Description   |
 | :------------ | :------------ |
-| ETag          | An indicator whether the admin-configured policy state has changed. If you have cached Etag value and it matches ETag from previous results from this API, there is no need to parse the response and cache the parsed results. Cache this value for calls to [process content](../api/userdatasecurityandgovernance-processcontent.md). |
+| ETag          | An indicator whether the admin-configured policy state changed. If you cached Etag value and it matches ETag from previous results from this API, there's no need to parse the response and cache the parsed results. Cache this value for calls to [process content](../api/userdatasecurityandgovernance-processcontent.md). |
 
 ## Response
 
@@ -78,6 +79,7 @@ The following example computes the protection scope for a user performing text u
 ```http
 POST https://graph.microsoft.com/v1.0/users/7c1f8f10-cba8-4a8d-9449-db4b876d1ef70/dataSecurityAndGovernance/protectionScopes/compute
 Content-type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
    "activities": "uploadText,downloadText",
@@ -92,13 +94,14 @@ Content-type: application/json
 
 #### Response
 
-The following example shows the response. It indicates that for the `uploadText` activity for the integrated application with id 83ef208a-0396-4893-9d4f-d36efbffc8bd, policies require inline evaluation. For the `uploadFile` activity for the integrated application with id 83ef208a-0396-4893-9d4f-d36efbffc8bd, policies require offline evaluation and trigger a `restrictAccess` action (likely blocking uploads based on contextual information, e.g. blocking uploads for specific users or group).
+The following example shows the response. It indicates that for the `uploadText` activity for the integrated application with id 83ef208a-0396-4893-9d4f-d36efbffc8bd, policies require inline evaluation. For the `uploadFile` activity for the integrated application with id 83ef208a-0396-4893-9d4f-d36efbffc8bd, policies require offline evaluation and trigger a `restrictAccess` action (likely blocking uploads based on contextual information; for example, blocking uploads for specific users or group).
 
 > **Note:** The response object shown here might be shortened for readability.
 
 ```http
 HTTP/1.1 200 OK
 Content-type: application/json
+Client-Request-Id: 50dc805c-3af4-42d9-ad16-a746235cc736
 
 {
   "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#Collection(microsoft.graph.policyUserScope)",