Skip to content

Add migrating between resources section #127497

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 2 commits into
base: main
Choose a base branch
from

Conversation

maciejporebski
Copy link
Contributor

Add a section to cover behaviour experienced when attempting to bind the same hostname to multiple SWA resources.

@Copilot Copilot AI review requested due to automatic review settings August 11, 2025 22:19
@prmerger-automator prmerger-automator bot requested a review from v1212 August 11, 2025 22:19
Copy link
Contributor

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

Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds documentation to explain the behavior and limitations when migrating custom domains between Azure Static Web Apps instances, specifically addressing the constraint that domains can only be bound to one resource per slice.

  • Adds a new section explaining domain binding limitations between Static Web Apps instances
  • Provides guidance on identifying which slice a resource belongs to
  • Offers solutions for migrating domains between instances in the same slice

Co-authored-by: Copilot <[email protected]>
Copy link
Contributor

Learn Build status updates of commit d22a886:

✅ Validation status: passed

File Status Preview URL Details
articles/static-web-apps/custom-domain.md ✅Succeeded

For more details, please refer to the build report.

Copy link
Contributor

Learn Build status updates of commit 0057091:

✅ Validation status: passed

File Status Preview URL Details
articles/static-web-apps/custom-domain.md ✅Succeeded

For more details, please refer to the build report.

@v-dirichards
Copy link
Contributor

@v1212

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

@prmerger-automator prmerger-automator bot added the aq-pr-triaged tracking label for the PR review team label Aug 12, 2025
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.

3 participants