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

[jofri] suggested changes to the documentation on api key registration #11893

Open
aosolis opened this issue Dec 4, 2024 · 1 comment
Open
Assignees
Labels
doc-enhancement If feedback is about suggested improvements/additions, but no evidence customer was blocked. needs-triage 🔍

Comments

@aosolis
Copy link
Collaborator

aosolis commented Dec 4, 2024

Type of issue

Missing information

Feedback

Observed:

image
image

Expected:
the developer only gets a permanent ID after publishing an app. So, the wording should be

For side-loaded and LOB apps, there is an internal app ID which isn't readily available. For these scenarios, lockdown the configuration to the tenant where it is used. For all other apps, after you publish your app to the store, bind this registration with your published app ID

Or something like that

Page URL

https://learn.microsoft.com/en-us/microsoftteams/platform/messaging-extensions/api-based-secret-service-auth#best-practices

Content source URL

https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/messaging-extensions/api-based-secret-service-auth.md

Author

@v-ypalikila

Document Id

79e1fd10-f2d6-90fe-5b54-59c36f894dc6

@sayali-MSFT
Copy link

@surbhigupta12 -Could you please help us to update the document.

@Prasad-MSFT Prasad-MSFT added the doc-enhancement If feedback is about suggested improvements/additions, but no evidence customer was blocked. label Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-enhancement If feedback is about suggested improvements/additions, but no evidence customer was blocked. needs-triage 🔍
Projects
None yet
Development

No branches or pull requests

6 participants