Skip to content

Commit 6bdae68

Browse files
authored
Merge pull request #24976 from microsoftgraph/main
Merge to publish.
2 parents 65ebc28 + 0256ccc commit 6bdae68

File tree

8 files changed

+63
-13
lines changed

8 files changed

+63
-13
lines changed

api-reference/beta/api/chatmessage-get.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -500,6 +500,7 @@ Content-type: application/json
500500
"reactions": [
501501
{
502502
"reactionType": "💯",
503+
"displayName": "Hundred points",
503504
"reactionContentUrl": null,
504505
"createdDateTime": "2024-02-14T22:07:36.3Z",
505506
"user": {
@@ -515,6 +516,7 @@ Content-type: application/json
515516
},
516517
{
517518
"reactionType": "custom",
519+
"displayName": "microsoft_teams",
518520
"reactionContentUrl": "https://graph.microsoft.com/beta/chats/19:bcf84b15c2994a909770f7d05bc4fe16@thread.v2/messages/1706763669648/hostedContents/aWQ9MC13dXMtZDExLTc3ZmI2NmY4MTMwMGI2OGEzYzRkOWUyNmU1YTc5ZmMyLHR5cGU9MSx1cmw9/$value",
519521
"createdDateTime": "2024-02-14T22:07:02.288Z",
520522
"user": {

api-reference/beta/api/teamsapp-delete.md

Lines changed: 26 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -25,14 +25,35 @@ You can also use this API to remove a submitted app from the review process.
2525

2626
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).
2727

28-
>**Note:** Only global administrators can call this API.
28+
> [!NOTE]
29+
> - The Directory.ReadWrite.All permission is supported only for backward compatibility. We recommend that you update your solutions to use an alternative permission and avoid using this permissions going forward.
30+
> - You can only use the AppCatalog.Submit permission to delete app definitions in review.
31+
> - Only global administrators can call this API.
32+
33+
Permissions for the following HTTP request:
2934

30-
<!-- { "blockType": "permissions", "name": "teamsapp_delete" } -->
35+
<!-- { "blockType": "ignored" } -->
36+
```http
37+
DELETE /appCatalogs/teamsApps/{id}
38+
```
39+
40+
<!-- { "blockType": "permissions", "name": "teamsapp_delete",   "requestUrls" : ["DELETE /appCatalogs/teamsApps/{id}"] } -->
3141
[!INCLUDE [permissions-table](../includes/permissions/teamsapp-delete-permissions.md)]
3242

33-
> [!NOTE]
34-
> - The Directory.ReadWrite.All permission is supported only for backward compatibility. We recommend that you update your solutions to use an alternative permission listed in the previous table and avoid using these permissions going forward.
35-
> - You can only use the AppCatalog.Submit permission to delete app definitions in review.
43+
Permissions for the following HTTP request:
44+
45+
<!-- { "blockType": "ignored" } -->
46+
```http
47+
DELETE appCatalogs/teamsApps/{appId}/appDefinitions/{appDefinitionId}
48+
```
49+
<!-- { "blockType": "permissions", "name": "teamsapp_delete",   "requestUrls" : ["DELETE appCatalogs/teamsApps/{appId}/appDefinitions/{appDefinitionId}"] } -->
50+
51+
|Permission type|Least privileged permissions|Higher privileged permissions|
52+
|:---|:---|:---|
53+
|Delegated (work or school account)|AppCatalog.Submit|AppCatalog.ReadWrite.All|
54+
|Delegated (personal Microsoft account)|Not supported.|Not supported.|
55+
|Application|Not supported.|Not supported.|
56+
3657

3758
## HTTP request
3859

api-reference/beta/resources/chatmessagereaction.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,9 @@ An entity of type `chatMessageReaction` is returned as part of the [Get channel
2222
| Property | Type | Description |
2323
|:-------------|:------------|:------------|
2424
|createdDateTime|DateTimeOffset|The timestamp type represents date and time information using ISO 8601 format and is always in UTC. For example, midnight UTC on Jan 1, 2014 is `2014-01-01T00:00:00Z`.|
25+
|displayName|String|The name of the reaction.|
2526
|reactionContentUrl|String|The hosted content URL for the custom reaction type. |
26-
|reactionType|String|Supported values are Unicode characters and `custom`. Some backward-compatible reaction types include `like`, `angry`, `sad`, `laugh`, `heart`, and `surprised`. |
27+
|reactionType|String|The reaction type. Supported values include Unicode characters, `custom`, and some backward-compatible reaction types, such as `like`, `angry`, `sad`, `laugh`, `heart`, and `surprised`. |
2728
|user|[chatMessageReactionIdentitySet](chatmessagereactionidentityset.md)|The user who reacted to the message.|
2829

2930
## JSON representation
@@ -43,6 +44,7 @@ The following JSON representation shows the resource type.
4344
{
4445
"createdDateTime": "String (timestamp)",
4546
"reactionContentUrl": "String",
47+
"displayName": "String",
4648
"reactionType": "String",
4749
"user": {"@odata.type": "microsoft.graph.chatMessageReactionIdentitySet"}
4850
}

api-reference/beta/resources/openidconnectsetting.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ Namespace: microsoft.graph
1313

1414
[!INCLUDE [beta-disclaimer](../../includes/beta-disclaimer.md)]
1515

16-
A complex type that contains the settings required to perform the OIDC request to the external authentication provider for an external authentication method. External authentication methods enable Microsoft Entra ID users to satisfy the second factor of multifactor authentication requirements using an external provider.
16+
A complex type that contains the settings required to perform the OIDC request to the external authentication provider for an [external authentication method](../resources/externalauthenticationmethodconfiguration.md). External authentication methods enable Microsoft Entra ID users to satisfy the second factor of multifactor authentication requirements using an external provider.
1717

1818
## Properties
1919
|Property|Type|Description|

changelog/Microsoft.Teams.Core.json

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5609,6 +5609,24 @@
56095609
"CreatedDateTime": "2024-05-06T18:15:55.2254479Z",
56105610
"WorkloadArea": "Teamwork and communications",
56115611
"SubArea": "Messaging"
5612+
},
5613+
{
5614+
"ChangeList": [
5615+
{
5616+
"Id": "a84dbdaa-5da8-4544-8a10-22c0790a9c5e",
5617+
"ApiChange": "Property",
5618+
"ChangedApiName": "displayName",
5619+
"ChangeType": "Addition",
5620+
"Description": "Added the **displayName** property to the [chatMessageReaction](https://learn.microsoft.com/en-us/graph/api/resources/chatmessagereaction?view=graph-rest-beta) resource to represent the reaction name [chatMessage](https://learn.microsoft.com/en-us/graph/api/resources/chatmessage?view=graph-rest-beta).",
5621+
"Target": "chatMessageReaction"
5622+
}
5623+
],
5624+
"Id": "a84dbdaa-5da8-4544-8a10-22c0790a9c5e",
5625+
"Cloud": "Prod",
5626+
"Version": "beta",
5627+
"CreatedDateTime": "2024-08-15T18:15:55.2254479Z",
5628+
"WorkloadArea": "Teamwork and communications",
5629+
"SubArea": "Messaging"
56125630
}
56135631
]
56145632
}

concepts/teams-messaging-overview.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -648,13 +648,14 @@ The **reactions** property represents reactions from other users on the message,
648648

649649
The following example shows a message with reactions.
650650

651-
>**Note:** The display name isn't always present.
651+
>**Note:** The display name isn't always present in the **user** property.
652652
653653
```json
654654
{
655655
"reactions": [
656656
{
657-
"reactionType": "like",
657+
"reactionType": "💯",
658+
"displayName": "Hundred points",
658659
"createdDateTime": "2022-01-18T23:41:57.573Z",
659660
"user": {
660661
"application": null,
@@ -674,13 +675,14 @@ The following example shows a message with a custom reaction.
674675

675676
>**Note:**
676677
> * Custom reactions are only available on the `/beta` endpoint.
677-
> * The display name isn't always present.
678+
> * The display name isn't always present for user.
678679
679680
```json
680681
{
681682
"reactions": [
682683
{
683684
"reactionType": "custom",
685+
"displayName": "microsoft_teams",
684686
"reactionContentUrl": "https://graph.microsoft.com/beta/chats/19:bcf84b15c2994a909770f7d05bc4fe16@thread.v2/messages/1706763669648/hostedContents/aWQ9MC13dXMtZDExLTc3ZmI2NmY4MTMwMGI2OGEzYzRkOWUyNmU1YTc5ZmMyLHR5cGU9MSx1cmw9/$value",
685687
"createdDateTime": "2024-02-14T22:07:02.288Z",
686688
"user": {

concepts/toc.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1140,7 +1140,7 @@ items:
11401140
displayName: Microsoft Graph error responses and error resource types
11411141
- name: Microsoft Entra service limits
11421142
displayName: Azure AD service limits and restrictions
1143-
href: /azure/active-directory/enterprise-users/directory-service-limits-restrictions?toc=/graph/toc.json
1143+
href: /azure/active-directory/enterprise-users/directory-service-limits-restrictions?context=graph/context
11441144
- name: Migrate
11451145
items:
11461146
- name: Azure AD Graph

concepts/whats-new-overview.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,13 @@ Enabled the `Spain` and `Mexico` values as supported regions for the **region**
4040
## August 2024: New in preview only
4141

4242
### Teamwork and communications | Calls and online meetings
43+
Use the **settings** property on [virtualEventTownhall](/graph/api/resources/virtualeventtownhall?view=graph-rest-beta&preserve-view=true) and [virtualEventWebinar](/graph/api/resources/virtualeventwebinar?view=graph-rest-beta&preserve-view=true) to get or set whether attendees receive email notifications for a town hall or webinar.
4344

44-
Use the **allowBreakoutRooms**, **allowLiveShare**, **allowPowerPointSharing**, and **allowWhiteboard** to indicate whether breakout rooms, live share, PowerPoint live, and whiteboard features are enabled in an [onlineMeeting](/graph/api/resources/onlinemeeting?view=graph-rest-beta&preserve-view=true) or [virtualEventSession](/graph/api/resources/virtualeventsession?view=graph-rest-beta&preserve-view=true).
45+
Removed the **meetingOrganizerId** property from the [callRecording](/graph/api/resources/callrecording?view=graph-rest-beta&preserve-view=true) and [callTranscript](/graph/api/resources/calltranscript?view=graph-rest-beta&preserve-view=true) resources in favor of the **meetingOrganizer** property.
46+
47+
### Teamwork and communications | Messaging
48+
49+
Use the **displayName** property on the [chatMessageReaction](https://learn.microsoft.com/en-us/graph/api/resources/chatmessagereaction?view=graph-rest-beta) resource to represent the reaction name [chatMessage](https://learn.microsoft.com/en-us/graph/api/resources/chatmessage?view=graph-rest-beta).
4550

4651
### Teamwork and communications | Online meeting
4752

@@ -58,7 +63,7 @@ Enabled the `Spain` and `Mexico` values as supported regions for the **region**
5863

5964
### Backup Storage
6065

61-
The new Microsoft 365 Backup Storage API enables partners to build customized versions of their applications that are integrated with the Microsoft 365 Backup Storage platform. This helps to ensure exceptionally fast recovery from typical business continuity and disaster recovery (BCDR) scenarios, such as ransomware attacks or accidental/malicious deletion or overwriting of content by employees. To explore the see, [Backup Storage](/concepts/backup-storage-concept-overview.md).
66+
The new Microsoft 365 Backup Storage API enables partners to build customized versions of their applications that are integrated with the Microsoft 365 Backup Storage platform. This helps to ensure exceptionally fast recovery from typical business continuity and disaster recovery (BCDR) scenarios, such as ransomware attacks or accidental/malicious deletion or overwriting of content by employees. For more information, see [Backup Storage](/graph/backup-storage-concept-overview).
6267

6368
### Customer booking
6469

0 commit comments

Comments
 (0)