Merge pull request #9766 from MartinM85/fix/status-codes

FaithOmbongi · web-flow · commit 666d7b46cbed · 2025-12-29T13:44:56.000+03:00
Fixes status codes
diff --git a/api-reference/beta/api/accesspackageassignmentrequest-cancel.md b/api-reference/beta/api/accesspackageassignmentrequest-cancel.md
@@ -114,5 +114,5 @@ The following example shows the response.
 } -->
 
 ```http
-HTTP/1.1 200 Status OK
+HTTP/1.1 200 OK
 ```
diff --git a/api-reference/beta/api/accessreview-update.md b/api-reference/beta/api/accessreview-update.md
@@ -54,7 +54,7 @@ The following table shows the properties that can be supplied when you update an
 
 
 ## Response
-If successful, this method returns a `204 Accepted` response code and an [accessReview](../resources/accessreview.md) object in the response body.
+If successful, this method returns a `202 Accepted` response code and an [accessReview](../resources/accessreview.md) object in the response body.
 
 ## Example
 
@@ -116,7 +116,7 @@ Content-type: application/json
   "@odata.type": "microsoft.graph.accessReview"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/accessreviewinstancedecisionitem-update.md b/api-reference/beta/api/accessreviewinstancedecisionitem-update.md
@@ -124,7 +124,7 @@ Content-Type: application/json
   "blockType": "response"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 ```
 
 
@@ -183,7 +183,7 @@ Content-Type: application/json
   "blockType": "response"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 ```
 
 ### Example 3: Update a applyResult on an accessReviewInstance
@@ -246,7 +246,7 @@ Content-Type: application/json
   "blockType": "response"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 ```
 
 <!--
diff --git a/api-reference/beta/api/channel-list-tabs.md b/api-reference/beta/api/channel-list-tabs.md
@@ -116,7 +116,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
@@ -213,7 +213,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/chat-list-operations.md b/api-reference/beta/api/chat-list-operations.md
@@ -108,7 +108,7 @@ GET https://graph.microsoft.com/beta/chats/19:c253a29b5f694b55a6baad8e83510af7@t
 }
 -->
 ``` http
-HTTP/1.1 202 OK
+HTTP/1.1 200 OK
 Content-Type: application/json
 
 {
diff --git a/api-reference/beta/api/chat-list-tabs.md b/api-reference/beta/api/chat-list-tabs.md
@@ -113,7 +113,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
@@ -240,7 +240,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/connectedorganization-update.md b/api-reference/beta/api/connectedorganization-update.md
@@ -55,7 +55,7 @@ The following table shows the properties that can be supplied when you update th
 
 ## Response
 
-If successful, this method returns a `204 Accepted` response code and a [connectedOrganization](../resources/connectedorganization.md) object in the response body.
+If successful, this method returns a `202 Accepted` response code and a [connectedOrganization](../resources/connectedorganization.md) object in the response body.
 
 ## Examples
 
@@ -117,7 +117,7 @@ Content-Type: application/json
 }
 -->
 ``` http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/educationclass-post-module.md b/api-reference/beta/api/educationclass-post-module.md
@@ -42,7 +42,7 @@ POST /education/classes/{id}/modules
 In the request body, supply a JSON representation of an [educationModule](../resources/educationmodule.md) object.
 
 ## Response
-If successful, this method returns a `201 OK` response code and an [educationModule](../resources/educationmodule.md) object in the request body.
+If successful, this method returns a `201 Created` response code and an [educationModule](../resources/educationmodule.md) object in the request body.
 
 ## Example
 
@@ -106,7 +106,7 @@ The following example shows the response.
   "@odata.type": "microsoft.graph.educationModule"
 } -->
 ```http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/filestoragecontainer-post-customproperty.md b/api-reference/beta/api/filestoragecontainer-post-customproperty.md
@@ -53,7 +53,7 @@ You can specify the following properties when you create a custom property.
 
 ## Response
 
-If successful, this method returns a `200 Created` response code.
+If successful, this method returns a `201 Created` response code.
 
 ## Examples
 
@@ -92,7 +92,7 @@ The following example shows the response. By default, the property isn't searcha
 }
 -->
 ```http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 ```
 ### Example 2: Create a custom searchable property
 
@@ -130,7 +130,7 @@ The following example shows the response.
 }
 -->
 ```http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 ```
 
 
diff --git a/api-reference/beta/api/post-post-attachments.md b/api-reference/beta/api/post-post-attachments.md
@@ -129,7 +129,7 @@ The following example shows the response.
   "name": "create_file_attachment_with_post"
 } -->
 ```http
-HTTP/1.1 202 Accpted
+HTTP/1.1 202 Accepted
 ```
 
 ### Example 2: Include an item attachment
@@ -289,7 +289,7 @@ The following example shows the response.
   "name": "create_reference_attachment_with_post"
 } -->
 ```http
-HTTP/1.1 202 Accpted
+HTTP/1.1 202 Accepted
 ```
 
 <!-- uuid: 8fcb5dbc-d5aa-4681-8e31-b001d5168d79
diff --git a/api-reference/beta/api/program-update.md b/api-reference/beta/api/program-update.md
@@ -109,7 +109,7 @@ Content-type: application/json
   "@odata.type": "microsoft.graph.program"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 Content-type: application/json
 
 {
diff --git a/api-reference/beta/api/send-device-command.md b/api-reference/beta/api/send-device-command.md
@@ -63,7 +63,7 @@ In the request body, supply a JSON representation of the command properties.
 ## Response
 
 ```http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 ```
 
 ```json
@@ -126,7 +126,7 @@ Content-Type: application/json; charset=utf-8
 } -->
 
 ```http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 
 {
   "id": "0158355AD4D680CC4E2994CC009EFFD7337D1B...",
@@ -183,7 +183,7 @@ Content-Type: application/json; charset=utf-8
 } -->
 
 ```http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 
 {
   "id": "0158355AD4D680CC4E2994CC009EFFD7EADA8307E96FF1C8D19B..",
diff --git a/api-reference/beta/api/site-post-sites.md b/api-reference/beta/api/site-post-sites.md
@@ -62,7 +62,7 @@ You can specify the following properties when you create a **site**.
 
 ## Response
 
-If successful, this method returns a `202 Created` response code and a [site](../resources/site.md) object in the response body. The response also contains a `Location` header, which contains the location of the [getOperationStatus](./site-getoperationstatus.md) that was created to handle the site creation operation. Check the status of the creation operation by making a GET request to this location.
+If successful, this method returns a `202 Accepted` response code and a [site](../resources/site.md) object in the response body. The response also contains a `Location` header, which contains the location of the [getOperationStatus](./site-getoperationstatus.md) that was created to handle the site creation operation. Check the status of the creation operation by making a GET request to this location.
 
 ## Examples
 
diff --git a/api-reference/beta/api/teamsasyncoperation-get.md b/api-reference/beta/api/teamsasyncoperation-get.md
@@ -115,7 +115,7 @@ The following example shows the response.
 }
 -->
 ```http
-HTTP/1.1 202 OK
+HTTP/1.1 200 OK
 Content-Type: application/json
 
 {
diff --git a/api-reference/v1.0/api/accesspackageassignmentrequest-cancel.md b/api-reference/v1.0/api/accesspackageassignmentrequest-cancel.md
@@ -97,5 +97,5 @@ POST https://graph.microsoft.com/v1.0/identityGovernance/entitlementManagement/a
 }
 -->
 ``` http
-HTTP/1.1 200 Status OK
+HTTP/1.1 200 OK
 ```
diff --git a/api-reference/v1.0/api/accessreviewinstancedecisionitem-update.md b/api-reference/v1.0/api/accessreviewinstancedecisionitem-update.md
@@ -119,7 +119,7 @@ Content-Type: application/json
   "blockType": "response"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 ```
 
 
@@ -178,7 +178,7 @@ Content-Type: application/json
   "blockType": "response"
 } -->
 ```http
-HTTP/1.1 204 Accepted
+HTTP/1.1 202 Accepted
 ```
 
 <!--
diff --git a/api-reference/v1.0/api/channel-list-tabs.md b/api-reference/v1.0/api/channel-list-tabs.md
@@ -113,7 +113,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
@@ -210,7 +210,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
diff --git a/api-reference/v1.0/api/chat-list-tabs.md b/api-reference/v1.0/api/chat-list-tabs.md
@@ -111,7 +111,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
@@ -238,7 +238,7 @@ The following example shows the response.
 -->
 
 ```http
-HTTP/1.1 200 Success
+HTTP/1.1 200 OK
 Content-type: application/json
 
 {
diff --git a/api-reference/v1.0/api/externalconnectors-external-post-connections.md b/api-reference/v1.0/api/externalconnectors-external-post-connections.md
@@ -119,7 +119,7 @@ The following example shows the response. Note that the **id**, **name**, and **
 }
 -->
 ``` http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 Content-Type: application/json
 
 {
diff --git a/api-reference/v1.0/api/filestoragecontainer-post-customproperty.md b/api-reference/v1.0/api/filestoragecontainer-post-customproperty.md
@@ -50,7 +50,7 @@ You can specify the following properties when you create a custom property.
 
 ## Response
 
-If successful, this method returns a `200 Created` response code.
+If successful, this method returns a `201 Created` response code.
 
 ## Examples
 
@@ -85,7 +85,7 @@ The following example shows the response. By default, the property isn't searcha
 }
 -->
 ``` http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 ```
 ### Example 2: Create a custom searchable property
 
@@ -119,5 +119,5 @@ The following example shows the response.
 }
 -->
 ``` http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 ```
diff --git a/api-reference/v1.0/api/post-post-attachments.md b/api-reference/v1.0/api/post-post-attachments.md
@@ -127,7 +127,7 @@ The following example shows the response.
   "name": "create_file_attachment_with_post"
 } -->
 ```http
-HTTP/1.1 202 Accpted
+HTTP/1.1 202 Accepted
 ```
 
 ### Example 2: Include an item attachment
@@ -288,7 +288,7 @@ The following example shows the response.
   "name": "create_reference_attachment_with_post"
 } -->
 ```http
-HTTP/1.1 202 Accpted
+HTTP/1.1 202 Accepted
 ```
 
 
diff --git a/api-reference/v1.0/api/security-ediscoverysearch-post-additionalsources.md b/api-reference/v1.0/api/security-ediscoverysearch-post-additionalsources.md
@@ -153,7 +153,7 @@ POST https://graph.microsoft.com/v1.0/security/cases/ediscoveryCases/17011798-ca
 The following example shows the response.
 
 ```http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 
 {
     "@odata.context": "https://graph.microsoft.com/v1.0/$metadata#security/cases/ediscoveryCases('17011798-ca63-4282-9cb3-0086f1042bfc')/searches('2f5cc5a6-9728-4ba0-acfa-edce25e91244')/additionalSources/$entity",
diff --git a/concepts/add-properties-profilecard.md b/concepts/add-properties-profilecard.md
@@ -77,10 +77,10 @@ Content-Type: application/json
 
 > **Note:** The `/organization/{organizationId}/settings` path is deprecated in the beta experience. Going forward, use the `/admin/people` path.
 
-If successful, the response returns a `201 OK` response code and a **profileCardProperty** object in the response body. The value for the `Alias` attribute is displayed on a user's profile card.
+If successful, the response returns a `201 Created` response code and a **profileCardProperty** object in the response body. The value for the `Alias` attribute is displayed on a user's profile card.
 
 ``` http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 Content-type: application/json
 
 {
@@ -150,12 +150,12 @@ Content-Type: application/json
 
 If a language isn't supported, the property name is shown with the default value.
 
-If successful, the response returns a `201 OK` response code and a **profileCardProperty** object in the response body. In this example, you can assume that the profile card displays **Kostenstelle** for all users who set their language settings to German on the profile card. For all other users, **Cost center** is displayed on the profile card.
+If successful, the response returns a `201 Created` response code and a **profileCardProperty** object in the response body. In this example, you can assume that the profile card displays **Kostenstelle** for all users who set their language settings to German on the profile card. For all other users, **Cost center** is displayed on the profile card.
 
 #### Response
 
 ``` http
-HTTP/1.1 201 OK
+HTTP/1.1 201 Created
 Content-type: application/json
 
 {
diff --git a/concepts/work-with-grading-categories.md b/concepts/work-with-grading-categories.md
@@ -302,7 +302,7 @@ The following example shows the response.
 >**Note:** The response object shown here might be shortened for readability.
 
 ```http
-HTTP/1.1 200 Created
+HTTP/1.1 201 Created
 Content-type: application/json
 
 {

Original file line number	Diff line number	Diff line change
`@@ -116,7 +116,7 @@ The following example shows the response.`
`116`	`116`	`-->`
`117`	`117`
`118`	`118`	```http
`119`		`-HTTP/1.1 200 Success`
	`119`	`+HTTP/1.1 200 OK`
`120`	`120`	`Content-type: application/json`
`121`	`121`
`122`	`122`	`{`
`@@ -213,7 +213,7 @@ The following example shows the response.`
`213`	`213`	`-->`
`214`	`214`
`215`	`215`	```http
`216`		`-HTTP/1.1 200 Success`
	`216`	`+HTTP/1.1 200 OK`
`217`	`217`	`Content-type: application/json`
`218`	`218`
`219`	`219`	`{`
Original file line number	Diff line number	Diff line change
`@@ -108,7 +108,7 @@ GET https://graph.microsoft.com/beta/chats/19:c253a29b5f694b55a6baad8e83510af7@t`
`108`	`108`	`}`
`109`	`109`	`-->`
`110`	`110`	``` http
`111`		`-HTTP/1.1 202 OK`
	`111`	`+HTTP/1.1 200 OK`
`112`	`112`	`Content-Type: application/json`
`113`	`113`
`114`	`114`	`{`
Original file line number	Diff line number	Diff line change
`@@ -113,7 +113,7 @@ The following example shows the response.`
`113`	`113`	`-->`
`114`	`114`
`115`	`115`	```http
`116`		`-HTTP/1.1 200 Success`
	`116`	`+HTTP/1.1 200 OK`
`117`	`117`	`Content-type: application/json`
`118`	`118`
`119`	`119`	`{`
`@@ -240,7 +240,7 @@ The following example shows the response.`
`240`	`240`	`-->`
`241`	`241`
`242`	`242`	```http
`243`		`-HTTP/1.1 200 Success`
	`243`	`+HTTP/1.1 200 OK`
`244`	`244`	`Content-type: application/json`
`245`	`245`
`246`	`246`	`{`
Original file line number	Diff line number	Diff line change
`@@ -55,7 +55,7 @@ The following table shows the properties that can be supplied when you update th`
`55`	`55`
`56`	`56`	`## Response`
`57`	`57`
`58`		-If successful, this method returns a `204 Accepted` response code and a [connectedOrganization](../resources/connectedorganization.md) object in the response body.
	`58`	+If successful, this method returns a `202 Accepted` response code and a [connectedOrganization](../resources/connectedorganization.md) object in the response body.
`59`	`59`
`60`	`60`	`## Examples`
`61`	`61`
`@@ -117,7 +117,7 @@ Content-Type: application/json`
`117`	`117`	`}`
`118`	`118`	`-->`
`119`	`119`	``` http
`120`		`-HTTP/1.1 204 Accepted`
	`120`	`+HTTP/1.1 202 Accepted`
`121`	`121`	`Content-type: application/json`
`122`	`122`
`123`	`123`	`{`