MicrosoftDocs
Add ARM template example for setting app settings in Azure App Service
This PR is to updated the document Configure an App Service app to include an ARM template example for setting app settings in Azure App Service.
@cloudsystemsarchitect : 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 0d8d518:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/app-service/configure-common.md | :warning:Warning | Details |
articles/app-service/configure-common.md
- Line 318, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 413, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 504, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 568, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 605, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
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}
Learn Build status updates of commit 58d59d9:
:warning: Validation status: warnings
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/app-service/configure-common.md | :warning:Warning | Details |
articles/app-service/configure-common.md
- Line 322, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 417, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 508, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 572, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set. - Line 609, Column 1: [Warning: invalid-tab-group - See documentation]
Tab group with different tab id set.
For more details, please refer to the build report.
Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@cephalin
Can you review the proposed changes?
- Note that the validation warnings need to be resolved before the PR can be merged.
- The commits also need to be moved to the private repo so that the new tabs can be reviewed on staging. Let us know if you'd like the PR review team's assistance.
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
@cephalin Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
@cephalin Would you add a comment to indicate what action to take on this PR?
Thanks!
I sent an email to the content owner today.
@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
I sent a Teams message to the content owner today.
@MicrosoftDocs/public-repo-pr-review-team
