[Doc Improvement][Add Multi-tenant contents]

msteams-platform/concepts/build-and-test/deep-link-teams.md

@@ -122,35 +122,35 @@ The query parameters are:
 
 * `channelId`: Channel ID of the conversation (URL encoded). For example, 19%3ATWLPKo8lD4v8zDxyw4FnDYY-ovnBJG5CSjmrHUAoOz41%40thread.tacv2.
 * `groupId`: Group ID of the file. For example, 72602e12-78ac-474c-99d6-f619710353a9.
-* `tenantId`: Tenant ID, such as 72f988bf-86f1-41af-91ab-2d7cd011db47.
+* `tenantId`: Tenant ID, such as aaaabbbb-0000-cccc-1111-dddd2222eeee.
 
 > [!Note]
 > You can get `channelId` and `groupId` in the URL from the team.
 
-Example: `https://teams.microsoft.com/l/team/19%3ATWLPKo8lD4v8zDxyw4FnDYY-ovnBJG5CSjmrHUAoOz41%40thread.tacv2/conversations?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47`
+Example: `https://teams.microsoft.com/l/team/19%3ATWLPKo8lD4v8zDxyw4FnDYY-ovnBJG5CSjmrHUAoOz41%40thread.tacv2/conversations?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=aaaabbbb-0000-cccc-1111-dddd2222eeee`
 
 ## Deep link to navigate to channel
 
 You can use the following deep link formats to navigate to particular channels:
 
 * **Standard channel**: `https://teams.microsoft.com/l/channel/<channelId>/<channelName>?groupId=<groupId>&tenantId=<tenantId>`
 
-  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47`
+  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=aaaabbbb-0000-cccc-1111-dddd2222eeee`
 
 * **Private channel**: `https://teams.microsoft.com/l/channel/<channelId>/<channelName>?groupId=<groupId>&tenantId=<tenantId>&ngc=true`
 
-  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&ngc=true`
+  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=aaaabbbb-0000-cccc-1111-dddd2222eeee&ngc=true`
 
 * **Shared channel**: `https://teams.microsoft.com/l/channel/<channelId>/<channelName>?groupId=<groupId>&tenantId=<tenantId>&ngc=true&allowXTenantAccess=true`
 
-  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&ngc=true&allowXTenantAccess=true`
+  Example: `https://teams.microsoft.com/l/channel/19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2/My%20example%20channel?groupId=72602e12-78ac-474c-99d6-f619710353a9&tenantId=aaaabbbb-0000-cccc-1111-dddd2222eeee&ngc=true&allowXTenantAccess=true`
 
 The query parameters are:
 
 * `channelId`: Channel ID of the conversation (URL encoded). For example, `19%3A9be3de4e70874c71a608dee9ba803ed3%40thread.tacv2`.
 * `channelName`: Name of the team's channel (URL encoded). For example, `My%20example%20channel`.
 * `groupId`: Group ID of the team. For example, `72602e12-78ac-474c-99d6-f619710353a9`.
-* `tenantId`: Tenant ID, such as `72f988bf-86f1-41af-91ab-2d7cd011db47`.
+* `tenantId`: Tenant ID, such as `aaaabbbb-0000-cccc-1111-dddd2222eeee`.
 * `ngc`: Indicates a next-generation channel. For private channels needs to be set to `true`.
 * `allowXTenantAccess`: Indicates a channel that can be accessed across tenant boundaries. For shared channels needs to be set to `true`.
 

msteams-platform/resources/samesite-cookie-update.md

@@ -48,7 +48,7 @@ SameSite cookie attributes are as follows:
 
 1. Enable the relevant SameSite setting for your cookies and validate that your apps and extensions continue to work in Teams.
 1. If your apps or extensions fail, make the necessary fixes prior to the Chrome 80 release.
-1. Microsoft internal partners can join the following team for more information or help with this issue: <https://teams.microsoft.com/l/team/19%3A08b594cd465e4c0491fb751e823802e2%40thread.skype/conversations?groupId=4d6d04cd-dbf0-43c8-a2ff-f80dd38be034&tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47>.
+1. Microsoft internal partners can join the following team for more information or help with this issue: <https://teams.microsoft.com/l/team/19%3A08b594cd465e4c0491fb751e823802e2%40thread.skype/conversations?groupId=4d6d04cd-dbf0-43c8-a2ff-f80dd38be034&tenantId=aaaabbbb-0000-cccc-1111-dddd2222eeee>.
 
 > [!NOTE]
 > You must set SameSite attributes to reflect the intended use for your cookies. Do not rely on default browser behavior. For more information, see [Developers: Get Ready for New SameSite=None; Secure Cookie Settings](https://blog.chromium.org/2019/10/developers-get-ready-for-new.html).

msteams-platform/toolkit/explore-Teams-Toolkit.md

@@ -63,6 +63,9 @@ From the task pane, you can see the following sections:
          * **Sign in to Microsoft 365**: Use your Microsoft 365 work or school account with a valid E5 subscription for building your app. If you don't have a valid account, you can join [Microsoft 365 developer program](https://developer.microsoft.com/microsoft-365/dev-program) to get a free account before you start.
 
         * **Sign in to Azure**: Use your Azure account for deploying your app on Azure. You can [create a free Azure account](https://azure.microsoft.com/free/) before you start.
+
+         > [!NOTE]
+         > By default, Teams Toolkit signs in to the home tenant of your Microsoft 365 and Azure accounts. If you want to deploy your Teams app to a guest tenant of your Microsoft 365 account or deploy Azure resources to a guest tenant of your Azure account, Teams Toolkit allows you to switch tenants for both accounts by clicking the switch button next to the account.
    :::column-end:::
 :::row-end:::
 

msteams-platform/toolkit/tools-prerequisites.md

@@ -44,6 +44,13 @@ Ensure that you have the following accounts before you start building your Teams
 |[Azure account](#azure-account)|Back-end resources on Azure.| JavaScript, TypeScript, SPFx, and C# or Blazor. |
 |[SharePoint collection site administrator account](#sharepoint-collection-site-administrator-account) |Deployment for hosting.| SPFx. |
 
+> [!NOTE]
+> If your Microsoft 365 account has multiple tenants, you can switch to any tenant in Teams Toolkit to deploy your Teams app. Following are the limitations:
+>
+> * You can use Teams Toolkit to deploy a Teams app to a guest tenant of your Microsoft 365 account. However, you might not be able to see your Teams app deployed to non-home tenants in the Teams Developer Portal. This is a limitation of the Teams Developer Portal.
+> * Publishing a Teams app for non-home tenants is not supported in Teams.
+> * Deploy an app to a non-home tenant is only supported for apps running in Teams. Apps running on other platforms, such as Outlook or Office.com, can't be deployed to non-home tenants.
+
 ### Microsoft 365 developer program
 
 > [!NOTE]