Building, integrating, or customizing apps and workflows within Microsoft Teams using developer tools and APIs
Hi Rich,
Thank you for posting your question in the Microsoft Q&A forum.
Could you please confirm whether the two accounts you mentioned (the Azure/Entra account used to create the app registration, and the Microsoft 365 account used in your Teams org) are in the same tenant (same directory), or in different tenants/directories?
If the accounts are in different tenants (cross-tenant scenario), your concerns could potentially be explained as follows:
Concern 1: App validation/upload across tenants & admin consent / service principal
If you are uploading and validating the Teams app in Tenant B, but the Microsoft Entra app registration was created in Tenant A, then Tenant B must have a corresponding service principal for that multi-tenant application. In practice, this usually requires admin consent (in the Teams tenant) so the app is “known” in the tenant where you are validating and installing the Teams app. Otherwise, validation and other checks can behave as if the app is not properly configured for the target tenant.
Concern 2: “Microsoft Teams hasn’t been provisioned on the tenant” indicates tenant subscription / Teams enablement
The Graph error message you received explicitly states: “Microsoft Teams hasn’t been provisioned on the tenant. Ensure the tenant has a valid Office365 subscription.” This generally points to the fact that the tenant context used for testing (i.e., the tenant that issued your access token) must have a valid Microsoft 365 subscription that have Microsoft Teams enabled; otherwise, the tenant can effectively be treated as “not using Teams,” which can lead to the provisioning-related error you’re seeing.
Looking forward your update on this issue.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.