MicrosoftDocs
Update documentation for API Management Client-Side/Mobile Applications
Hello, I thought this was a nice addition to talking about proper OAuth 2.0 flow and showing the inherit dangers to client-side/mobile applications using subscription keys. Prior to merge, If approved, I would like some feedback on final edits. If denied, please let me know what is missing and why this should not be included. Thank you kindly
@conradj3 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
![prmerger-automator[bot] avatar](https://avatars.githubusercontent.com/u/22479449?v=4 "Published by a pub.dev verified publisher"){kind=small}
Learn Build status updates of commit 6c4abf1:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/api-management/api-management-subscriptions.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
![learn-build-service-prod[bot] avatar](https://avatars.githubusercontent.com/in/237442?v=4 "Published by a pub.dev verified publisher"){kind=small}
PRMerger Results
| Issue | Description |
|---|---|
| File Change Percent | This PR contains file(s) with more than 30% file change. |
@conradj3 : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.
Learn Build status updates of commit 2576cc7:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/api-management/api-management-subscriptions.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
PRMerger Results
| Issue | Description |
|---|---|
| File Change Percent | This PR contains file(s) with more than 30% file change. |
@dlepow
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
Learn Build status updates of commit c46a70e:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/api-management/api-management-subscriptions.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
Learn Build status updates of commit 3c78328:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/api-management/api-management-subscriptions.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
PRMerger Results
| Issue | Description |
|---|---|
| File Change Percent | This PR contains file(s) with more than 30% file change. |
I sent an email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
@dlepow
Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
I sent a Teams message to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
I sent email to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
