Fix incorrect tab mentioned for frontend app registration#248
Merged
crickman merged 1 commit intomicrosoft:mainfrom Aug 25, 2023
Rainson12:fix-incorrect-tab-for-app-registration
Merged
Fix incorrect tab mentioned for frontend app registration#248crickman merged 1 commit intomicrosoft:mainfrom Rainson12:fix-incorrect-tab-for-app-registration
crickman merged 1 commit intomicrosoft:mainfrom
Rainson12:fix-incorrect-tab-for-app-registration
Conversation
github-actions
Bot
added
documentation
TaoChenOSU
approved these changes
Aug 25, 2023
crickman
approved these changes
Aug 25, 2023
teamleader-dev
pushed a commit
to vlink-group/chat-copilot
that referenced
this pull request
Oct 7, 2024
) ### Motivation and Context This fixes incorrect documentation when trying to setup the azure application permissions for the frontend. ### Description When adding the api permissions for the first time to the frontend, the "My APIs" will actually be empty:  (you can ignore the "hidden" - thats another app we have developed) Instead the previously created exposure of the backend can only be found in the "APIs my organization uses" tab: 
kb0039
pushed a commit
to aaronba/chat-copilot
that referenced
this pull request
Jan 8, 2025
) ### Motivation and Context This fixes incorrect documentation when trying to setup the azure application permissions for the frontend. ### Description When adding the api permissions for the first time to the frontend, the "My APIs" will actually be empty:  (you can ignore the "hidden" - thats another app we have developed) Instead the previously created exposure of the backend can only be found in the "APIs my organization uses" tab: 
jdtoombs
pushed a commit
to jdtoombs/chat-copilot
that referenced
this pull request
Apr 10, 2025
…ebapp (microsoft#248) Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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
3 participants
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.
Motivation and Context
This fixes incorrect documentation when trying to setup the azure application permissions for the frontend.
Description
When adding the api permissions for the first time to the frontend, the "My APIs" will actually be empty:
(you can ignore the "hidden" - thats another app we have developed)
Instead the previously created exposure of the backend can only be found in the "APIs my organization uses" tab:
