chore(KNO-14013): clarify teams prereqs and publication process#1514
Draft
cellomatt wants to merge 1 commit into
Draft
chore(KNO-14013): clarify teams prereqs and publication process#1514cellomatt wants to merge 1 commit into
cellomatt wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
cellomatt
commented
Jul 1, 2026
Comment on lines
+98
to
+104
| <a | ||
| href="https://learn.microsoft.com/en-us/microsoftteams/platform/concepts/deploy-and-publish/appsource/publish" | ||
| target="_blank" | ||
| rel="noreferrer noopener" | ||
| > | ||
| app submission guide | ||
| </a>{" "} |
Member
Author
There was a problem hiding this comment.
This link originally pointed to https://learn.microsoft.com/en-us/partner-center/marketplace-offers/add-in-submission-guide. I opted to update it here because this new link is to Teams Store-specific instructions, and the step-by-step within those instructions links to the original marketplace guide.
Publishing to the Teams Store automatically publishes to the Marketplace as well.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR attempts to clarify the process for getting your MS Teams bot published as a Teams app to the Microsoft Teams Store. It adds a new section on publication to the Teams store, and also moves all of the Microsoft-side setup under the Prerequisites header so that How to connect Teams with Knock only includes the steps for dashboard configuration.
It also puts some of the existing information about multi-tenant bot deprecation and expected (lengthy) submission timelines into callouts to draw attention to those details.
TODO:
There's still an open question about the correct way to configure Graph API w/ Entra in the case that you don't have a legacy multi-tenant bot. Working to see if we can update that guidance as part of this PR, otherwise we'll need to tweak the existing language slightly. I have an open request with Microsoft Support but have so far gotten no response.