Skip to content

Conversation

@st-jan
Copy link

@st-jan st-jan commented Nov 7, 2025

Clarified authentication requirements for storage accounts without public network access.
We learned through interactions with Microsoft that Shared Access Signatures and Storage Account Keys cannot be used in this instance.

Clarified authentication requirements for storage accounts without public access.
@prmerger-automator
Copy link
Contributor

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

@v-dirichards
Copy link
Contributor

refreshing the build

@v-dirichards v-dirichards reopened this Nov 7, 2025
@v-dirichards v-dirichards requested a review from Copilot November 7, 2025 16:06
Copy link
Contributor

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 updates the COPY INTO documentation to clarify authentication requirements for Azure storage accounts that have public network access disabled. The update informs users that Shared Access Signatures and Storage Account Keys are not supported in this scenario, and that EntraID authentication is required instead.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@v-dirichards
Copy link
Contributor

@WilliamDAssafMSFT

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 Nov 7, 2025
@learn-build-service-prod
Copy link
Contributor

Learn Build status updates of commit 0473e86:

✅ Validation status: passed

File Status Preview URL Details
docs/t-sql/statements/copy-into-transact-sql.md ✅Succeeded

For more details, please refer to the build report.

@WilliamDAssafMSFT
Copy link
Contributor

Thanks @st-jan for contacting Microsoft with a contribution to our product documentation. If you can provide any more non-person, non-identifying details about your environment and the products used, that would be helpful. Requires some confirmation on our side.

It could take from a few business days to a few weeks to confirm your change internally. We'll contact you if we need further information, and you'll receive an email message each time we "@mention" you in a comment.

By opening a pull request, you're helping the authors add your approved change directly to the documentation. If the article is updated with your commit, GitHub will list you as an article contributor.

Thanks again for this feedback. Your suggestions help improve our documentation.

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