Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: add multi-tenant contents #12063

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

HuihuiWu-Microsoft
Copy link

No description provided.

@acrolinxatmsft1
Copy link
Collaborator

Acrolinx Scorecards

We currently enforce a minimum score of 80.

Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article Score Issues Scorecard Processed
msteams-platform/toolkit/explore-Teams-Toolkit.md 89 9 link
msteams-platform/toolkit/tools-prerequisites.md 81 35 link

More info about Acrolinx

Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Copy link
Contributor

Learn Build status updates of commit fdc19c1:

✅ Validation status: passed

File Status Preview URL Details
msteams-platform/assets/images/teams-toolkit-v2/teams toolkit fundamentals/switchTenants.png ✅Succeeded View
msteams-platform/toolkit/explore-Teams-Toolkit.md ✅Succeeded View
msteams-platform/toolkit/tools-prerequisites.md ✅Succeeded View

For more details, please refer to the build report.

For any questions, please:

@@ -54,6 +54,7 @@ From the task pane, you can see the following sections:
:::row:::
:::column span="":::
:::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/accounts1_1.png" alt-text="Screenshot shows the Accounts section.":::
:::image type="content" source="../assets/images/teams-toolkit-v2/teams toolkit fundamentals/switchTenants.png" alt-text="Screenshot shows the switch tenant button.":::
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why this screenshot didn't show the tenant info?

@@ -62,6 +63,8 @@ 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: When you sign in to Microsoft 365 or Azure account, your signed in tenant is your home tenant by default. You can switch to other tenants manually by clicking the switch button on signed in account item.
Copy link
Collaborator

@summzhan summzhan Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rephrase to "Note that Teams Toolkit by default will sign in home tenant of your Microsoft 365 account and Azure account. If you want to deploy your Teams app to guest tenant of your Microsoft 365 account, or you want to deploy Azure resources to the guest tenant of your Azure account, Teams Toolkit allow you to switch tenant for both account by clicking the switch button besides that account."

@@ -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 could switch to either tenant to develop Teams app. But there're several known limitations that should be aware of:
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"In case your Microsoft 365 account has multiple tenants, you could switch to any tenant in Teams Toolkit to deploy Teams app. Known limitations that you should keep in mind:"

> [!NOTE]
> If your Microsoft 365 account has multiple tenants, you could switch to either tenant to develop Teams app. But there're several known limitations that should be aware of:
>
> * Multi-tenant is not supported by TDP yet. You may not be able to see your Teams app provisioned in non-home tenants from Teams Dev portal.
Copy link
Collaborator

@summzhan summzhan Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"You can use Teams Toolkit to deploy Teams app to guest tenant of M365 account, while you may not be able to see your Teams app deployed to non-home tenants in Teams Developer Portal. This is a limitation of Teams Developer Portal now."

>
> * Multi-tenant is not supported by TDP yet. You may not be able to see your Teams app provisioned in non-home tenants from Teams Dev portal.
> * Publishing Teams app of non-home tenants is not well supported in Teams.
> * Multi-tenant is only supported for Teams app. Extending Teams app to other hubs(Outlook, Office.com) is not supported under non-home tenants.
Copy link
Collaborator

@summzhan summzhan Jan 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Deploy app to non-home tenant is only supported for app running in Teams. Apps running in other platform like Outlook, Office.com can not deploy to non-home tenants."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants