Skip to content

Conversation

JaredMSFT
Copy link
Contributor

updating public preview information.

@prmerger-automator
Copy link
Contributor

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

@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 7fb8f2c:

✅ Validation status: passed

File Status Preview URL Details
articles/postgresql/flexible-server/concepts-elastic-clusters-limitations.yml ✅Succeeded

For more details, please refer to the build report.

@prmerger-automator
Copy link
Contributor

PRMerger Results

Issue Description
Yaml File(s) This PR includes changes to .yml file(s) owned by another author.
File Change Percent This PR contains file(s) with more than 30% file change.

@v-dirichards
Copy link
Contributor

Hi @JaredMSFT - This pull request was opened in the public repo. PMs should work in the private repo, per the Microsoft Docs contributor guide. We can keep this PR open for review and merge, but would you make future content updates in the private repo? Thank you!


@mulander Could you take a look?

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@prmerger-automator prmerger-automator bot added the aq-pr-triaged C+L Pull Request Review Team label label Oct 16, 2025
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

Updates documentation to reflect current public preview feature availability and limitations for elastic clusters in Azure Database for PostgreSQL Flexible Server.

  • Standardizes several answers and updates feature support status (e.g., Entra ID auth now supported, replica availability added).
  • Rewords and reorganizes FAQ entries (extensions, migrations, networking) for clarity.

Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.

Comment on lines +49 to +52
answer: Currently, GEO backups & GEO restore aren't supported during the public preview.

- question: Is Long Term Retention (LTR) supported?
answer: Currently, Long Term Retention isn't supported during the preview.
answer: Currently, Long Term Retention isn't supported during the public preview.
Copy link

Copilot AI Oct 16, 2025

Choose a reason for hiding this comment

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

The terminology alternates between "public preview" and "the preview" within closely related answers. For consistency and clarity, standardize on one term (e.g., "public preview") across these lines.

Copilot uses AI. Check for mistakes.

answer: Migrations to/from elastic clusters can be done with pg_dump, pg_restore, and pgcopydb. Any other tool working with standard PostgreSQL should work.

- question: Can I convert my existing Public Preview instance to General Availability (GA) elastic clusters?
answer: If you have created any elastic clusters during the Public Preview phase, you are required to re-create them once the feature becomes Generally Available. If this raises concerns, or if you need help determining whether your server meets the necessary requirements, please contact us by going to the Azure portal, selecting your Azure Postgres resource, and following the instructions in the banner.
Copy link

Copilot AI Oct 16, 2025

Choose a reason for hiding this comment

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

Multiple sentences use double spaces after periods, which is inconsistent with typical single-space style in the rest of the document. Remove the extra spaces to maintain formatting consistency.

Copilot uses AI. Check for mistakes.

@JaredMSFT JaredMSFT closed this Oct 20, 2025
@JaredMSFT JaredMSFT deleted the ec-limitations-updates branch October 20, 2025 14:55
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