Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Update service-tier-hyperscale-frequently-asked-questions-faq.yml#9695

Merged
Jak-MS merged 3 commits intoMicrosoftDocs:livefrom
SeanCowburnMSFT:patch-1
Mar 1, 2024
Merged

Update service-tier-hyperscale-frequently-asked-questions-faq.yml#9695
Jak-MS merged 3 commits intoMicrosoftDocs:livefrom
SeanCowburnMSFT:patch-1

Conversation

@SeanCowburnMSFT
Copy link
Copy Markdown
Contributor

Changed message around AHB for Hyperscale.

Changed message around AHB for Hyperscale.
@prmerger-automator
Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 127111c:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@Jak-MS
Copy link
Copy Markdown
Contributor

Jak-MS commented Feb 29, 2024

@dimitri-furman

  • Can you review this PR?
  • IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#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 Feb 29, 2024
@dimitri-furman
Copy link
Copy Markdown
Contributor

@arvindshmicrosoft can you please review?

Comment thread azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml Outdated
Comment thread azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml Outdated
…estions-faq.yml

Co-authored-by: Arvind Shyamsundar <arvindsh@microsoft.com>
@prmerger-automator
Copy link
Copy Markdown
Contributor

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

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit ca136a0:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit ca136a0:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

…estions-faq.yml

Co-authored-by: Arvind Shyamsundar <arvindsh@microsoft.com>
@arvindshmicrosoft
Copy link
Copy Markdown
Contributor

@dimitri-furman I'm good with these changes. Do you want to also take a look?

@learn-build-service-prod
Copy link
Copy Markdown
Contributor

Learn Build status updates of commit 8bcb48f:

✅ Validation status: passed

File Status Preview URL Details
azure-sql/database/service-tier-hyperscale-frequently-asked-questions-faq.yml ✅Succeeded

For more details, please refer to the build report.

For any questions, please:

@arvindshmicrosoft
Copy link
Copy Markdown
Contributor

#sign-off

@prmerger-automator
Copy link
Copy Markdown
Contributor

Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @dimitri-furman

@dimitri-furman
Copy link
Copy Markdown
Contributor

#sign-off

@Jak-MS Jak-MS merged commit 065e1ba into MicrosoftDocs:live Mar 1, 2024
@prmerger-automator
Copy link
Copy Markdown
Contributor

PR 9695 has been merged from SeanCowburnMSFT:patch-1 to MicrosoftDocs:live by Jak-MS.

@SeanCowburnMSFT, @dimitri-furman, @arvindshmicrosoft

@SeanCowburnMSFT SeanCowburnMSFT deleted the patch-1 branch March 4, 2024 18:53
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.

4 participants