Updates from: 04/17/2021 03:12:09
Service Microsoft Docs article Related commit history on GitHub Change details
platform Create Apps For Teams Meetings https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/apps-in-teams-meetings/create-apps-for-teams-meetings.md
To use the `userContext` API to route requests accordingly, see [Teams SDK](../t
Messaging extension works as expected when a user is in an in-meeting view and the user can post compose message extension cards. AppName in-meeting is a tooltip that states the app name in-meeting U-bar.
+> [!NOTE]
+> Use version 1.9.0 of [Teams SDK](https://docs.microsoft.com/javascript/api/overview/msteams-client?view=msteams-client-js-latest&preserve-view=true) to upload side panel, as versions prior to it do not support side panel.
+ #### In-meeting dialog The in-meeting dialog box can be used to engage participants during the meeting and collect information or feedback during the meeting. Use the [`NotificationSignal`](/graph/api/resources/notifications-api-overview?view=graph-rest-beta&preserve-view=true) API to signal that a bubble notification must be triggered. As part of the notification request payload, include the URL where the content to be shown is hosted.
platform Teams Apps In Meetings https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/apps-in-teams-meetings/teams-apps-in-meetings.md
keywords: teams apps meetings user participant role api + # Apps in Teams meetings Meetings enable collaboration, partnership, informed communication, and shared feedback in an inclusive and active forum. The meeting app can deliver a user experience for each stage of the meeting lifecycle including pre-meeting, in-meeting and post-meeting app experience, depending on the attendee's status.
Tabs allow team members to access services and content in a specific space withi
Γ£ö Permissioned users can add apps while in the meeting.
-Γ£ö When loaded in the context of a meeting, apps can leverage the Teams Client SDK to access the `meetingId`, `userMri`, and `frameContext` to appropriately render the experience.
+Γ£ö When loaded in the context of a meeting, apps can leverage the Teams client SDK to access the `meetingId`, `userMri`, and `frameContext` to appropriately render the experience.
Γ£ö Exporting a result of a survey or poll notifies the users that the results successfully downloaded.
-Γ£ö An app is visible in a Teams meeting in the side panel or the in-meeting dialog box. Use the in-meeting dialog to showcase actionable content for meeting participants. *See* [Create Apps for Teams meetings](create-apps-for-teams-meetings.md).
+Γ£ö An app is visible in a Teams meeting in the side panel or the in-meeting dialog box. Use the in-meeting dialog box to showcase actionable content for meeting participants. For more information, see [create apps for Teams meetings](create-apps-for-teams-meetings.md).
> [!NOTE] > Your app manifest specifies that your tab is [optimized for side panel](create-apps-for-teams-meetings.md#during-a-meeting), that is where it is displayed. It can also be part of a share-tray experience, subject to specified design guidelines.
The following user types identify what each user can do and what they can access
* **In-tenant**: In-tenant users belong to the organization and have credentials in Azure Active Directory (AAD) for the tenant. They are usually full-time, onsite, or remote employees. An in-tenant user can be an organizer, presenter, or attendee. * **Guest**: A guest is a participant from another organization invited to access Teams or other resources in the organization's tenant. Guests are added to your organizationΓÇÖs AAD and have the same Teams capabilities as a native team member with access to team chats, meetings, and files. A guest user can be an organizer, presenter, or attendee. For more information, see [guest access in Teams](/microsoftteams/guest-access). * **Federated or external**: A federated user is an external Teams user in another organization who has been invited to join a meeting. These users have valid credentials with federated partners and are authorized by Teams. They do not have access to your teams or other shared resources from your organization. Guest access is a better option for external users to have access to teams and channels. For more information, see [manage external access in Teams](/microsoftteams/manage-external-access).
-* **Anonymous**: Anonymous users do not have an AAD identity and are not federated with a tenant. The anonymous participant is like an external user, but their identity is not projected in the meeting. Anonymous users are not able to access apps in a meeting window. An anonymous user cannot be an organizer but can be a presenter or attendee.
+* **Anonymous**: Anonymous users do not have an AAD identity and are not federated with a tenant. The anonymous participant is like an external user, but their identity is not projected in the meeting. An anonymous user cannot be an organizer but can be a presenter or an attendee.
+
+> [!NOTE]
+> Anonymous users inherit the global default user-level app permission policy. For more information, see [Manage Apps](/microsoftteams/non-standard-users#anonymous-user-in-meetings-access).
+
+The following table provides the user types and what features each user can access:
+
+| User type | Tabs | Bots | Messaging extensions | Adaptive Cards | Task modules | In-meeting dialog |
+| :-- | :-- | :-- | :-- | :-- | :-- | :-- |
+| Anonymous user | Not available | Not available | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from an Adaptive Card are allowed. | Not available |
+| Guest that is part of the tenant AAD | Interaction is allowed. Creating, updating, and deleting are not allowed. | Not available | Not available | Interactions in the meeting chat are allowed. | Interactions in the meeting chat from an Adaptive Card are allowed. | Available |
+| Federated | Not available | Not available | Not available | Not available | Not available | Not available |
## See also
platform Deep Links https://github.com/MicrosoftDocs/msteams-docs/commits/master/msteams-platform/concepts/build-and-test/deep-links.md
You can create links to information and features within Teams. Examples where cr
> Γ£ö Directly navigates to the deeplink url. > > **Bot**:
-> Γ£ö Deeplink in card body - Opens in browser first.
-> Γ£ö Deeplink added to OpenURL action in Adaptive Card - Directly navigates to the deeplink url.
-> Γ£ö Hyperlink markdown text in the card - Opens in browser first.
+> Γ£ö Deeplink in card body: Opens in browser first.
+> Γ£ö Deeplink added to OpenURL action in Adaptive Card: Directly navigates to the deeplink url.
+> Γ£ö Hyperlink markdown text in the card: Opens in browser first.
> > **Chat**:
-> Γ£ö Text message hyperlink markdown : Directly navigates to deeplink url.
-> Γ£ö Link pasted in general chat conversation - Directly navigates to deeplink url.
+> Γ£ö Text message hyperlink markdown: Directly navigates to deeplink url.
+> Γ£ö Link pasted in general chat conversation: Directly navigates to deeplink url.
## Deep linking to your tab
You can create deep links to private chats between users by specifying the set o
As an example use case, if you are returning an Office 365 user profile from your bot as a card, this deep link can allow the user to easily chat with that person.
-### Generating a deep link to a chat
+### Generate a deep link to a chat
Use this format for a deep link that you can use in a bot, connector, or messaging extension card:
The query parameters are:
To use this deep link with your bot, you can specify this as the URL target in your card's button or tap action through the `openUrl` action type.
+## Generate deep links to file in channel
+
+The following deep link format can be used in a bot, connector, or messaging extension card:
+
+`https://teams.microsoft.com/I/file/5E0154FC-F2B4-4DA5-8CDA-F096E72C0A80?tenantId=<tenantid>&fileType=<filetype>&objectURL=<objectURL>&baseUrl=<baseURL>&serviceName=<Name>&threadId=<threadid>&groupId=<groupId>`
+
+The query parameters are:
+
+* `tenantId`: Tenant ID example, 0d9b645f-597b-41f0-a2a3-ef103fbd91bb
+* `fileType`: Supported file type, such as docx, pptx, xlsx, and pdf
+* `objectUrl`: Object URL of the file, https://microsoft.sharepoint.com/teams/(filepath)
+* `baseUrl`: Base URL of the file, https://microsoft.sharepoint.com/teams
+* `serviceName`: Name of the service, app ID
+* `threadId`: The threadId is the team ID of the team where the file is stored. It is optional and cannot be set for files stored in a user's OneDrive folder. threadId - 19:f8fbfc4d89e24ef5b3b8692538cebeb7@thread.skype
+* `groupId`: Group ID of the file, ae063b79-5315-4ddb-ba70-27328ba6c31e
+
+Following is the sample format of deeplink to files:
+
+`https://teams.microsoft.com/l/file/5E0154FC-F2B4-4DA5-8CDA-F096E72C0A80 ?tenantId=0d9b645f-597b-41f0-a2a3-ef103fbd91bb&fileType=pptx&objectUrl=https%3A%2F%2Fmicrosoft.sharepoint.com%2Fteams%2FActionPlatform%2FShared%20Documents%2FFC7-%20Bot%20and%20Action%20Infra%2FKaizala%20Actions%20in%20Adaptive%20Cards%20-%20Deck.pptx&baseUrl=https%3A%2F%2Fmicrosoft.sharepoint.com%2Fteams%2FActionPlatform&serviceName=teams&threadId=19:f8fbfc4d89e24ef5b3b8692538cebeb7@thread.skype&groupId=ae063b79-5315-4ddb-ba70-27328ba6c31e`
+
+### Serialization of this object:
+```
+{
+tenantId: "0d9b645f-597b-41f0-a2a3-ef103fbd91bb",
+filetype: = "pptx",
+objectUrl: "https://microsoft.sharepoint.com/teams/ActionPlatform/Shared Documents/FC7- Bot and Action Infra/Kaizala Actions in Adaptive Cards - Deck.pptx",
+baseUrl: "https://microsoft.sharepoint.com/teams/ActionPlatform",
+serviceName: "teams",
+threadId: = "19:f8fbfc4d89e24ef5b3b8692538cebeb7@thread.skype",
+groupId: "ae063b79-5315-4ddb-ba70-27328ba6c31e"
+}
+```
## Deep links for SharePoint Framework tabs The following deep link format can be used in a bot, connector or messaging extension card:
The following deep link format can be used in a bot, connector or messaging exte
The query parameters are:
-* `appID` - Your manifest ID **fe4a8eba-2a31-4737-8e33-e5fae6fee194**.
-* `entityID` - The item ID that you provided when [configuring the tab](~/tabs/how-to/create-tab-pages/configuration-page.md). For example, **tasklist123**.
-* `entityWebUrl` - An optional field with a fallback URL to use if the client does not support rendering of the tab - https://tasklist.example.com/123 or https://tasklist.example.com/list123/task456.
-* `entityName` - A label for the item in your tab, to use when displaying the deep link, Task List 123 or Task 456.
+* `appID`: Your manifest ID fe4a8eba-2a31-4737-8e33-e5fae6fee194.
+* `entityID`: The item ID that you provided when [configuring the tab](~/tabs/how-to/create-tab-pages/configuration-page.md). For example, **tasklist123**.
+* `entityWebUrl`: An optional field with a fallback URL to use if the client does not support rendering of the tab - https://tasklist.example.com/123 or https://tasklist.example.com/list123/task456.
+* `entityName`: A label for the item in your tab, to use when displaying the deep link, Task List 123 or Task 456.
Example: https://teams.microsoft.com/l/entity/fe4a8eba-2a31-4737-8e33-e5fae6fee194/tasklist123?webUrl=https://tasklist.example.com/123&TaskList
Example: `https://teams.microsoft.com/l/meeting/new?subject=test%20subject&atten
The query parameters are: * `attendees`: The optional comma-separated list of user IDs representing the attendees of the meeting. The user performing the action is the meeting organizer. The User ID field currently only supports the Azure AD UserPrincipalName, typically an email address.
-* `startTime`: The optional start time of the event. This should be in [long ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), for example ΓÇ£2018-03-12T23:55:25+02:00ΓÇ¥.
+* `startTime`: The optional start time of the event. This should be in [long ISO 8601 format](https://en.wikipedia.org/wiki/ISO_8601), for example *2018-03-12T23:55:25+02:00*.
* `endTime`: The optional end time of the event, also in ISO 8601 format. * `subject`: An optional field for the meeting subject. * `content`: An optional field for the meeting details field.