Skip to content

Add ARM template example for setting app settings in Azure App Service #126294

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

codebypatrickleung
Copy link

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.

Copy link
Contributor

@cloudsystemsarchitect : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change.

Copy link
Contributor

Learn Build status updates of commit 0d8d518:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/app-service/configure-common.md ⚠️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:

Copy link
Contributor

Learn Build status updates of commit 58d59d9:

⚠️ Validation status: warnings

File Status Preview URL Details
articles/app-service/configure-common.md ⚠️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:

@Court72
Copy link
Contributor

Court72 commented Mar 24, 2025

@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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Mar 24, 2025
@v-dirichards
Copy link
Contributor

@cephalin Can you review this old PR and determine whether it needs to be closed or merged?

@MicrosoftDocs/public-repo-pr-review-team

@v-dirichards
Copy link
Contributor

@cephalin Would you add a comment to indicate what action to take on this PR?

Thanks!

@v-ccolin
Copy link
Contributor

I sent an email to the content owner today.

@MicrosoftDocs/public-repo-pr-review-team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants