Forum Widgets
Latest Discussions
Is it possible for a Teams app to automatically create an Azure Key Vault during installation?
Hi everyone, I’m developing a custom Teams app that needs access to Azure Key Vault. Right now, users must manually provide: Key Vault URL Tenant ID Client ID Client Secret Instead, I’d like the app to automatically create a Key Vault in the user’s tenant during installation. Is this possible? If so, what permissions/consent are required from the admin? If not, what’s the best practice to simplify this setup? Thanks!Solvedmuradqr5hSep 10, 2025Copper Contributor165Views0likes3Comments
Enabling Cross-Tenant Authentication for Teams Apps with Single-Tenant Bot
Hello Team, I am working on implementing authentication for a Teams application using the Microsoft 365 Agents SDK. Following Microsoft’s current guidance, I have: Registered a single-tenant Azure AD bot. Integrated Azure AD authentication. Prepared for AppSource distribution as the long-term supported method for cross-tenant availability. However, I am still facing challenges in reliably enabling sign-in for external users from other tenants. Specifically: The cross-tenant sign-in flow remains unclear. Validating authentication across multiple tenants is difficult without official end-to-end guidance. Existing samples and documentation primarily address single-tenant or internal-only scenarios. As of now, authentication for external users is still difficult to get working and validate consistently across tenants. Could you provide detailed guides, samples, or best practices for: Enabling authentication for external users in this single tenant + AppSource distribution model. Recommended patterns for testing cross-tenant authentication before AppSource submission. Any roadmap considerations for simplifying this scenario. This would help ensure Teams apps can meet compliance requirements while still delivering a smooth sign-in experience for users across organizations. Thank You, ChetanSolvedchetanoptimusSep 01, 2025Copper Contributor218Views0likes6Comments
Consent popup
Hi everyone, I’m reaching out for clarification regarding a popup that intermittently appears when users interact with our notification only bot, specifically when attempting to open a task module. After clicking "Agree" it shows "Enjoy using" and then appeared again. When clicking on Privacy/Terms of use nothing happens, while Permissions lead to opening another popup with endless loading, after closing it consent popup stops appearing for this app. Context: Sideloaded; Only a bot is declared in the manifest; App registration: Registered in Azure as multi-tenant with personal accounts enabled, SSO is not used; Interaction: Task module is triggered via Adaptive Card with Action.Submit, "msteams": { "type": "task/fetch" }; We’ve seen it only a few times in one tenant. It does not appear in most other sessions. Can someone tell if this is a bug or if there are some specific conditions that trigger this popup? Thanks in advance!SolvedDenys-FokinJun 30, 2025Copper Contributor200Views0likes6CommentsPowershell for creating a Auto Attendant
Hello I would like to create an Auto Attendant through Powershell. The command is New-CsAutoAttendant Teams keeps asking about the DefaultCallFlow. I would like to hardcode the command like this: New-CsAutoAttendant -Name "xx" -LanguageId "fr-FR" -TimeZoneId "Romance Standard Time" How do I add the DefaultCallFlow and then redirect it to an external number Regards JFM_12Solved167Views0likes4Comments
Urgent: Teams app publishing process blocked - app does not appear in the store after approval
Hello everyone, i am contacting you regarding a problem with the publishing of my Microsoft Teams app that started yesterday and is blocking my development work. Problem description: After developing a new version of my MS Teams app, I can no longer successfully publish it in my organization. The app is uploaded in the Developer Portal, released in the Teams Admin Center, but then does not appear in the Teams App Store under "Built for your org", so I cannot test it. Chronology: I am an admin in my organization and am developing a Teams app Before yesterday, the publishing process went smoothly: Upload in the Developer Portal → Appearance in the App Store → Test Yesterday, a colleague installed the app for testing purposes Since then, I can no longer publish new versions (they do not appear in the App Store) The upload and release in the Admin Center work without an error message However, the app does not appear in the App Store afterwards, neither in the desktop client nor in the web client Attempts have already been made to solve this: Completely restarted Teams client several times App version increased in manifest (to 1.2.0) App deleted and re-uploaded in Developer Portal App deleted and re-released in Teams Admin Center Waited for a delay of several hours Cleared cache (as far as possible on Mac) Test in web client (with the same result) Special observations: In the Mac client, the button "Upload a custom app" is grayed out with the note to contact my IT admin (I am the admin myself) On the Service Health Page, there is an active incident with the ID MO1093370 that affects Microsoft Teams I suspect that the issue is related to the current service degradation, which is described in the health page as "An infrastructure component is not processing requests as efficiently as expected" and explicitly affects Microsoft Teams. Is there a way to fix or work around this issue so that I can continue my development work? Can you confirm whether there is a connection with the current service degradation? Thank you in advance for your help. Best regards MichaelSolvedMRingtunatusJun 14, 2025Copper Contributor238Views0likes4Comments
Approvals API only working in the default environment
I am using the beta Approvals API (approvalItem resource type - Microsoft Graph beta | Microsoft Learn) for a proof of concept and have noticed that it works great in the Personal Productivity (Default) environment, but I get 404 non found errors when trying to access approvals in other environments. I've tried adding the app registration I'm using to the environment as an S2S app with Sys Admin privileges and added the org API endpoint to the app itself but neither solved it. Is this intended behavior?SolvedAJBerry223Jun 05, 2025Former Employee105Views0likes3Comments
Maximum # of scopes in manifest 1.21
I am looking at the 1.21 version of the https://developer.microsoft.com/json-schemas/teams/v1.21/MicrosoftTeams.schema.json and I see the definition below for the scopes properties. It only allows a maximum of 3 items, which means that you cannot allow all 4 available values to be defined. E.g. the following definition in the bot manifest would be invalid scopes: ["team", "personal", "groupChat", "copilot"] Is this intentional? Thank you. "scopes": { "type": "array", "description": "Specifies whether the bot offers an experience in the context of a channel in a team, in a 1:1 or group chat, or in an experience scoped to an individual user alone. These options are non-exclusive.", "maxItems": 3, "items": { "enum": [ "team", "personal", "groupChat", "copilot" ] } }, "commandLists": { "type": "array", "maxItems": 3, "description": "The list of commands that the bot supplies, including their usage, description, and the scope for which the commands are valid. A separate command list should be used for each scope.", "items": { "type": "object", "additionalProperties": false, "properties": { "scopes": { "type": "array", "description": "Specifies the scopes for which the command list is valid", "maxItems": 3, "items": { "enum": [ "team", "personal", "groupChat", "copilot" ] } }SolvedbertoldJun 03, 2025Copper Contributor64Views0likes1CommentWhat is the recommended bot type for multi-tenant bots?
According to this https://learn.microsoft.com/en-us/azure/bot-service/bot-service-quickstart-registration?view=azure-bot-service-4.0&tabs=multitenant#bot-identity-information multi-tenant bots cannot be created after July 31, 2025. Another option to reach tenants other than ours is to use incoming webhooks. However, according to this https://learn.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/add-incoming-webhook?tabs=newteams%2Cdotnet, incoming webhooks will be deprecated at the end of 2025. I would like to create a bot that can be deployed to any Microsoft Teams outside our organization. What is the recommended approach? Thank you.SolvedbertoldJun 03, 2025Copper Contributor1.6KViews1like4CommentsDelay in Teams Proactive Notification Popups (Internal and Customer Impact)
We are currently experiencing an issue with Microsoft Teams, both internally and among our customers. Specifically, there is a noticeable delay in the appearance of proactive notification popups. In many instances, these notifications are delayed by approximately 5 to 10 seconds after the triggering event using ms botframework sdk. This issue affects the responsiveness of our Teams-based applications and workflows, particularly in time-sensitive use cases. The delay has been observed consistently across different environments, which suggests it may not be limited to a specific configuration or network. We would appreciate your assistance in investigating this matter. If there are any known issues, recommended diagnostics, or configuration adjustments that could help mitigate this behavior, we would be grateful for your guidance. Thank you very much for your support.Solvedjames099Jun 03, 2025Copper Contributor315Views0likes6Comments
Resources
Tags
- microsoft teams1,759 Topics
- developer1,367 Topics
- meetings236 Topics
- Chat229 Topics
- Administrator152 Topics
- Settings115 Topics
- calling107 Topics
- files68 Topics
- teams56 Topics
- devices53 Topics