Remove status field

FaithOmbongi · FaithOmbongi · commit 3a2ab633b939 · 2026-02-25T11:39:56.000+03:00
diff --git a/concepts/includes/known-issues/authentication.md b/concepts/includes/known-issues/authentication.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The consent page shows that the command-line app that caters to PowerShell and CLI is from an unverified publisher.
 
 #### Workaround
@@ -31,8 +29,6 @@ Connect-MgGraph -AppId "{your-own-app-id}" -Scopes "scope"
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Under certain circumstances, pre-consent for cloud solution provider (CSP) apps may not work for some of your customer tenants.
 
 For apps using delegated permissions, when using the app for the first time with a new customer tenant, you might receive this error after sign-in: `AADSTS50000: There was an error issuing a token`.
@@ -67,6 +63,4 @@ To unblock development and testing, you can use the following workaround.
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Cloud solution provider (CSP) apps must acquire tokens from the Azure AD (v1) endpoints to successfully call Microsoft Graph in their partner-managed customers. Currently, acquiring a token through the newer Azure AD v2.0 endpoint is not supported.
diff --git a/concepts/includes/known-issues/calendar.md b/concepts/includes/known-issues/calendar.md
@@ -12,6 +12,4 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 An app with delegated permissions returns `HTTP 403 Forbidden` when attempting to attach large files to an Outlook message or event that is in a shared or delegated mailbox. With delegated permissions, [createUploadSession](/graph/api/attachment-createuploadsession) succeeds only if the message or event is in the signed-in user's mailbox.
diff --git a/concepts/includes/known-issues/change-notifications.md b/concepts/includes/known-issues/change-notifications.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When a subscription for a Teams app installation change notification is created, if the scope is specific to or includes chats, upgrade events/notifications will not be delivered to the subscriber.
 
 For example: If a customer subscribes to `/appCatalogs/teamsApps/{teams-app-id}/installations?$filter=(scopeInfo/scope eq 'groupChat')`, they will not receive notifications for upgrade/update events. However, they will receive other notifications regarding installations and deletions.
diff --git a/concepts/includes/known-issues/customer-booking.md b/concepts/includes/known-issues/customer-booking.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Getting the list of **bookingBusinesses** fails with the following error code when an organization has several Bookings businesses and the account making the request is not an administrator:
 
 ```json
diff --git a/concepts/includes/known-issues/delta-query.md b/concepts/includes/known-issues/delta-query.md
@@ -12,6 +12,4 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 OData context is sometimes returned incorrectly when tracking changes to relationships.
diff --git a/concepts/includes/known-issues/device-app-management.md b/concepts/includes/known-issues/device-app-management.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Accessing and updating deployment audiences on deployment resources created via Intune is not currently supported.
 
 - Listing deployment audience members and listing deployment audience exclusions returns `404 Not Found`.
diff --git a/concepts/includes/known-issues/groups.md b/concepts/includes/known-issues/groups.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When a non-admin user calls the [Create group](/graph/api/group-post-groups) API, [Update group](/graph/api/group-update) API, or [Upsert group](/graph/api/group-upsert) API and adds their user ID in the request body in the **owners@odata.bind** collection, the request fails with a `400 Bad Request` error code with the message "Request contains a property with duplicate values." A non-admin user can't explicitly add themselves as the group owner.
 
 #### Workaround
@@ -29,8 +27,6 @@ By default, a non-admin user who is creating a security or Microsoft 365 group t
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [List group members](/graph/api/group-list-members) API operation on the v1.0 endpoint currently doesn't return any service principals that might be members of the queried group.
 
 #### Workaround
diff --git a/concepts/includes/known-issues/identity-access.md b/concepts/includes/known-issues/identity-access.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The following usage of query parameters that target **subscribedSkus** and **domain** entities might not return the expected results:
 
 - Use of `$search` on both **subscribedSkus** or **domain** entities
@@ -32,8 +30,6 @@ To prevent any disruption to your business processes, we recommend that you modi
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [Create internalDomainFederation](/graph/api/domain-post-federationconfiguration), [Update internalDomainFederation](/graph/api/internaldomainfederation-update), and [Delete internalDomainFederation](/graph/api/internaldomainfederation-delete) might require you to grant consent to the *Directory.AccessAsUser.All* permission. This requirement is a temporary workaround till we provide a more granular delegated permission for managing federated domains.
 
 ### Claims mapping policy might require consent to additional permissions
@@ -43,8 +39,6 @@ The [Create internalDomainFederation](/graph/api/domain-post-federationconfigura
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [claimsMappingPolicy](/graph/api/resources/claimsmappingpolicy) API might require consent to both the *Policy.Read.All* and *Policy.ReadWrite.ConditionalAccess* permissions for the `LIST /policies/claimsMappingPolicies` and `GET /policies/claimsMappingPolicies/{id}` methods, as follows:
 
 - If no **claimsMappingPolicy** objects are available to retrieve in a LIST operation, either permission is sufficient to call this method.
@@ -59,6 +53,4 @@ In the future, either permission will be sufficient to call both methods.
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [conditionalAccessPolicy](/graph/api/resources/conditionalaccesspolicy) API currently requires consent to the *Policy.Read.All* permission to call the POST and PATCH methods. In the future, the *Policy.ReadWrite.ConditionalAccess* permission will enable you to read policies from the directory.
diff --git a/concepts/includes/known-issues/json-batching.md b/concepts/includes/known-issues/json-batching.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Individual requests can depend on other individual requests. Currently, requests can only depend on a single other request, and must follow one of these three patterns:
 
 - **Parallel** - no individual request states a dependency in the **dependsOn** property.
diff --git a/concepts/includes/known-issues/mail.md b/concepts/includes/known-issues/mail.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When you make `/delta` calls to the messages API using immutable Ids in some cases (for example when a message moves out of a folder and is then moved back in), you might miss some change notifications.
 
 ### The comment parameter for creating a draft does not become part of the message body
@@ -23,6 +21,4 @@ When you make `/delta` calls to the messages API using immutable Ids in some cas
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The **comment** parameter for creating a reply or forward draft ([createReply](/graph/api/message-createreply), [createReplyAll](/graph/api/message-createreplyall), [createForward](/graph/api/message-createforward)) does not become part of the body of the resultant message draft.
diff --git a/concepts/includes/known-issues/query-parameters.md b/concepts/includes/known-issues/query-parameters.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 As per RFC 3986 and as described in [Encoding query parameters](/graph/query-parameters#encoding-query-parameters), reserved characters in query strings must be percent-encoded. For example, the syntax for `$search` on a group name like "Hiking&Recreation" is as follows:
 
 ```http
@@ -55,8 +53,6 @@ Prefer: legacySearch=true
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The following limitations apply to query parameters:
 
 - Multiple namespaces are not supported.
diff --git a/concepts/includes/known-issues/search.md b/concepts/includes/known-issues/search.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When you use Microsoft Graph APIs to create an external connection with a broken adaptive card for the result layout, the first call fails with a `503 Service Unavailable` error. Then the second call fails with `409 Conflict` error that indicates that a connection with the same name already exists.
 
 Although the first request failed with a 503 response, the connection was still created. However, the adaptive card template was not registered because it is broken.
diff --git a/concepts/includes/known-issues/sites-lists.md b/concepts/includes/known-issues/sites-lists.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When querying followed sites through Microsoft Graph, the response might have incorrect results and those results might not match the results from following content in SharePoint.
 
 #### Workaround
diff --git a/concepts/includes/known-issues/teamwork-communications.md b/concepts/includes/known-issues/teamwork-communications.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 In some edge cases, a request to list **participants_v2** for a **callRecord** might return an incomplete list.
 
 #### Workaround
@@ -27,8 +25,6 @@ You can utilize the existing **participants** property of a **callRecord** for a
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When recording bot applications enable Bot Grouping, the number of participants shown by the Teams client as being recorded isn't accurate. Because the participants are grouped, the displayed number of participants being recorded is lower than the actual number.
 
 #### Workaround
@@ -42,8 +38,6 @@ Disable bot grouping to show an accurate count.
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 In the **callRecord** participant resource, application/bot participants are currently represented by the [communicationsUserIdentity](/graph/api/resources/communicationsuseridentity) instead of [communicationsApplicationIdentity](/graph/api/resources/communicationsapplicationidentity).
 
 #### Workaround
@@ -57,8 +51,6 @@ Use the user agent **headerValue** on the [participantEndpoint](/graph/api/resou
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When the same application or user is joining the same meeting using multiple endpoints, and the roster notification mode is delta roster, the participant roster updates provided by Communications SDK might not capture the additional endpoints added to the ongoing call.
 
 #### Workaround
@@ -72,8 +64,6 @@ Legacy mode for roster supports the multi-endpoint use case. Use the SDK version
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The release of the KBs introduced an issue with applications developed with the Communication Calling SDKs.
 
 The Microsoft Graph `AnswerAsync` method throws an exception when the bot tries to answer incoming calls. This is related to the following Windows updates:
@@ -94,8 +84,6 @@ Roll back the KBs pending an updated release of the SDK.
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Change tracking (`/delta`) requests to [getAllTranscripts](/graph/api/callrecording-delta) or [getAllRecordings](/graph/api/calltranscript-delta) might return items that were already synced in earlier requests.
 
 This happens when the meeting had other non-related updates, such as adding participants, notes, or files.
@@ -111,8 +99,6 @@ For every item in the response, check the **createdDateTime** of the recording o
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [getAllRecordings](/graph/api/onlinemeeting-getallrecordings) API does not return recordings for meetings that don't have transcription enabled.
 
 ### APIs that export online meeting artifacts might not return nextLink when the request uses the $top query parameter
@@ -122,8 +108,6 @@ The [getAllRecordings](/graph/api/onlinemeeting-getallrecordings) API does not r
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When you call the [getAllRecordings](/graph/api/onlinemeeting-getallrecordings) or [getAllTranscripts](/graph/api/onlinemeeting-getalltranscripts) APIs, passing the `$top` filter might not return the `@odata.nextLink`, even when there are more items to export.
 
 #### Workaround
@@ -137,8 +121,6 @@ Do not pass `$top` query parameter until the issue is fixed.
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When a newly created tenant sends a [list members of team](/graph/api/team-list-members) request using advanced Azure AD query capabilities, an HTTP 401 error occurs.
 
 #### Workaround
@@ -153,8 +135,6 @@ When a newly created tenant sends a [list members of team](/graph/api/team-list-
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When you call the [clone team](/graph/api/team-clone) method, if the source team contains more than one owner, only one owner is preserved in the cloned team. The other owners become members of the new cloned team. It is not possible to choose or configure which owner is retained as the owner of the new team.
 
 #### Workaround
@@ -168,8 +148,6 @@ Use the [Add members](/graph/api/team-post-members) method after you clone the t
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When you create a channel, if you use special characters in your channel name, the [Get filesFolder](/graph/api/channel-get-filesfolder) API will return a `400 Bad Request` error response. When you create a channel, make sure that the **displayName** for the channel does not:
 
 - Include any of the following special characters: `~ # % & * { } + / \ : < > ? | ' "`.
@@ -182,8 +160,6 @@ When you create a channel, if you use special characters in your channel name, t
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The API calls for `teams/{team-id}/incomingChannels` and `teams/{team-id}/allChannels` return the `@odata.id` property which you can use to access the channel and run other operations on the channel object. If you call the URL returned from the `@odata.id` property, the request fails with the following error when it tries to access the cross-tenant shared channel:
 
 ```http
@@ -215,8 +191,6 @@ Remove the `/tenants/{tenant-id}` part from the URL before you call the API to a
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 All the requests to filter team members by roles expect either a **skipToken** parameter or a **top** parameter in the request, but not both. If both the parameters are passed in the request, the **top** parameter will be ignored.
 
 ### Unable to filter team members by roles
@@ -226,8 +200,6 @@ All the requests to filter team members by roles expect either a **skipToken** p
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Role query filters along with other filters `GET /teams/team-id/members?$filter=roles/any(r:r eq 'owner') and displayName eq 'dummy'` might not work. The server might respond with a `BAD REQUEST`.
 
 ### View meeting details menu is not available on Microsoft Teams client
@@ -237,8 +209,6 @@ Role query filters along with other filters `GET /teams/team-id/members?$filter=
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The Microsoft Teams client does not show the **View Meeting details** menu for channel meetings created via the cloud communications API.
 
 ### Sensitivity label does not show up in the Teams UI
@@ -248,8 +218,6 @@ The Microsoft Teams client does not show the **View Meeting details** menu for c
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Sensitivity Labels that are applied to Teams at times do not show up in the Teams UI, even though it can clearly be seen in both the underlying SharePoint site and in the Admin Center.
 
 ### Some properties for chat members might be missing in the response to a GET request
@@ -259,8 +227,6 @@ Sensitivity Labels that are applied to Teams at times do not show up in the Team
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 In certain instances, the **tenantId**/**email**/**displayName** property for the individual members of a chat might not be populated on a `GET /chats/chat-id/members` or `GET /chats/chat-id/members/membership-id` request.
 
 ### Get chats limit updated for expand members
@@ -270,8 +236,6 @@ In certain instances, the **tenantId**/**email**/**displayName** property for th
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 This API works differently in one or more national clouds. For details, see [Implementation differences in national clouds](/graph/teamwork-national-cloud-differences). When `$expand=members` is included, this API returns a maximum of 25 items, even if a larger `$top` value is specified.
 
 ### layoutType property returns `null` when listing all channels
@@ -281,6 +245,4 @@ This API works differently in one or more national clouds. For details, see [Imp
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 In the current beta release, the **layoutType** property returns `null` when listing all channels.
diff --git a/concepts/includes/known-issues/users.md b/concepts/includes/known-issues/users.md
@@ -12,8 +12,6 @@ ms.localizationpriority: medium
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 The [getAllTranscripts](/graph/api/onlinemeeting-getalltranscripts) API might return transcript content URLs for some meetings that don't have any transcribed words. Calls to the content URL for those meetings will return an error.
 
 #### Workaround
@@ -27,8 +25,6 @@ Verify that the meeting has been transcribed and if there's valid content. If th
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 When querying users through Microsoft Graph, the **showInAddressList** property may not indicate the same status shown in Microsoft Exchange. We recommend you manage this functionality directly with Microsoft Exchange through the Microsoft 365 admin center and not to use this property in Microsoft Graph.
 
 ### Access to a user's profile photo is limited
@@ -38,8 +34,6 @@ When querying users through Microsoft Graph, the **showInAddressList** property
   "ms.reviewer": ""
 } -->
 
-**Status**: Active
-
 Reading and updating a user's profile photo is only possible if the user has a mailbox. Failure to read or update a photo, in this case, results in the following error:
 
 ```json
