diff --git a/api-reference/beta/api/chats-getallmessages.md b/api-reference/beta/api/chats-getallmessages.md index 07d11167fd3..180846222d0 100644 --- a/api-reference/beta/api/chats-getallmessages.md +++ b/api-reference/beta/api/chats-getallmessages.md @@ -35,29 +35,30 @@ GET /users/{id | user-principal-name}/chats/getAllMessages ## Optional query parameters -This method supports [date range parameters](/graph/query-parameters) to customize the response, as shown in the following example. - -```http -GET /users/{id}/chats/getAllMessages?$top=50&$filter=lastModifiedDateTime gt 2020-06-04T18:03:11.591Z and lastModifiedDateTime lt 2020-06-05T21:00:09.413Z -``` -Use the `model` query parameter to specify the [payment model](/graph/teams-licenses) that applies to your scenario, as shown in the following examples. +You can use the `model` query parameter, which supports the values `A` and `B`, based on the preferred [licensing and payment model](/graph/teams-licenses), +as shown in the following examples. +If no `model` parameter is specified, [evaluation mode](/graph/teams-licenses#evaluation-mode-default-requirements) will be used. ```http GET /users/{id | user-principal-name}/chats/getAllMessages?model=A GET /users/{id | user-principal-name}/chats/getAllMessages?model=B ``` ->**Note:** If you don't specify a payment model in your query, the default [evaluation mode](/graph/teams-licenses#evaluation-mode-default-requirements) will be used. -This method supports different filtering scenarios: +This operation also supports [date range parameters](/graph/query-parameters) to customize the response, as shown in the following example. + +``` http +GET /users/{id}/chats/getAllMessages?$top=50&$filter=lastModifiedDateTime gt 2020-06-04T18:03:11.591Z and lastModifiedDateTime lt 2020-06-05T21:00:09.413Z +``` +This method also supports `$filter`. The following table lists examples. -|Scenario | Filter parameter |Possible values | +|Scenario | `$filter` parameter |Possible values | |:-----------------------------------------|:---------------------------------------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------| |Get messages sent by user identity type |$filter=from/user/userIdentityType eq '{teamworkUserIdentityType}' |aadUser, onPremiseAadUser, anonymousGuest, federatedUser, personalMicrosoftAccountUser, skypeUser, phoneUser| |Get messages sent by application type |$filter=from/application/applicationIdentityType eq '{teamworkApplicationIdentity}' |aadApplication, bot, tenantBot, office365Connector, outgoingWebhook | -|Get messages sent by user id |$filter=from/user/id eq '{oid}' || +|Get messages sent by user ID |$filter=from/user/id eq '{oid}' || |Get control(system event) messages |$filter=messageType eq 'systemEventMessage' || |Exclude control (system event) messages |$filter=messageType ne 'systemEventMessage' || ->**Note:** These filter clauses can be joined using the `or` operator. A filter clause can appear more than once in a query, and it can filter on a different value each time it appears within the query. +>**Note:** These filter clauses can be joined by using the `or` operator. A filter clause can appear more than once in a query, and it can filter on a different value each time it appears within the query. ## Request headers | Header | Value | diff --git a/api-reference/v1.0/api/chats-getallmessages.md b/api-reference/v1.0/api/chats-getallmessages.md index d1e66a49118..79344fa5081 100644 --- a/api-reference/v1.0/api/chats-getallmessages.md +++ b/api-reference/v1.0/api/chats-getallmessages.md @@ -33,16 +33,14 @@ GET /users/{id | user-principal-name}/chats/getAllMessages ## Optional query parameters -You can use `model` query parameter, which supports the values `A` and `B`, based on the preferred [licensing and payment model](/graph/teams-licenses), +You can use the `model` query parameter, which supports the values `A` and `B`, based on the preferred [licensing and payment model](/graph/teams-licenses), as shown in the following examples. -If no `model` is specified, [evaluation mode](/graph/teams-licenses#evaluation-mode-default-requirements) is used. +If no `model` parameter is specified, [evaluation mode](/graph/teams-licenses#evaluation-mode-default-requirements) is used. ```http GET /users/{id | user-principal-name}/chats/getAllMessages?model=A GET /users/{id | user-principal-name}/chats/getAllMessages?model=B ``` -If no `model` is specified, [evaluation mode](/graph/teams-licenses#evaluation-mode-default-requirements) is used. - This operation also supports [date range parameters](/graph/query-parameters) to customize the response, as shown in the following example. ``` http diff --git a/concepts/teams-licenses.md b/concepts/teams-licenses.md index 2ba63261125..08da002e050 100644 --- a/concepts/teams-licenses.md +++ b/concepts/teams-licenses.md @@ -18,8 +18,8 @@ The following table lists the APIs and [change notification](/graph/api/subscrip |:------------------|:---------------| | [Change notification](/graph/api/subscription-post-subscriptions) `resources`: | A, B | | [Change notification](/graph/api/subscription-post-subscriptions) `resources`: | B | -| APIs: | A, B | -| APIs, when updating the `policyViolation` property: | A | +| [Export APIs](/microsoftteams/export-teams-content): | A, B | +| PATCH APIs, when updating the `policyViolation` property: | A | | Teams meeting APIs: | No model parameter | > [!NOTE] @@ -209,6 +209,7 @@ You can also call the [getTeamsUserActivityUserDetail](/graph/api/reportroot-get | Scenario | Details | |:-------------------------|:--------| +| Why was the number of messages billed higher than the number of messages in my Teams? | If your app is retrieving the same message multiple times, it is billed for multiple times. One way to avoid this is to use [change notifications](/graph/api/subscription-post-subscriptions) instead of [export APIs](/microsoftteams/export-teams-content). If you must use export APIs, make sure to use filters (for example, `$filter=lastModifiedDateTime`, `$filter=from`). | | Did billing actually started on July 5? | Yes, we're onboarding partners in phases. For continued access, follow the instructions on [Enable metered Microsoft 365 APIs and services](/graph/metered-api-setup) to set up an active Azure subscription for billing purposes. | What should I expect after setting up an Azure subscription? | Billing is effective immediately. You can monitor the costs as described in the [View the costs billed for the metered Microsoft Teams APIs](#view-the-costs-billed-for-the-metered-microsoft-teams-apis) section above. | | Do I need to provide an Azure subscription if my application isn't calling metered APIs? | We recommend that you provide an Azure subscription because most scenarios use metered APIs. |