Update storage-use-azcopy-blobs-synchronize.md

[prkana]

Added new scenerio and example

[learn-build-service-prod]

Learn Build status updates of commit 4110279:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/storage/common/storage-use-azcopy-blobs-synchronize.md	⚠️Warning		Details

articles/storage/common/storage-use-azcopy-blobs-synchronize.md

• Line 128, Column 56: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/products/storage/storage-explorer' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prkana]

Line 128, Column 56: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/products/storage/storage-explorer' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

This is Microsoft official site to download the "Azure Storage Explorer"

[v-regandowner]

@prkana - Thank you for your contribution. Would you take a moment to sign the Contributor License Agreement (CLA)? After the CLA is signed, someone can review your pull request. Thanks!

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

[prkana]

I agree with the agreement.

@microsoft-github-policy-service agree [company="{Microsoft}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.
@microsoft-github-policy-service agree company="Microsoft"

[prkana]

@microsoft-github-policy-service agree

@microsoft-github-policy-service agree company="Microsoft"

[prmerger-automator]

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

[v-dirichards]

@normesta

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

[normesta]

Thanks for the contribution. I added some suggestions for you to review and accept. Question - what motivates the introduction of a SAS section here. To keep things simple and consistent, all examples exclude the token. We have a section in each article which states that. We also have a section in the AzCopy overview which shows an example of using SAS should folks need to. In general, SAS is not the preferred method of auth. That is why we avoid promoting it in examples. If you have some specific business need for including a section here for SAS, feel free. I plan to sweep through this content a bit later in the year and do a better job driving eyeballs to our guidance about SAS so that we don't have to include article-specific SAS examples. At any rate, thank you for showing interest. Please review my suggestions. Cheers!

[learn-build-service-prod]

Learn Build status updates of commit a967214:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/storage/common/storage-use-azcopy-blobs-synchronize.md	⚠️Warning		Details

articles/storage/common/storage-use-azcopy-blobs-synchronize.md

• Line 128, Column 56: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/products/storage/storage-explorer' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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:

• Try searching the learn.microsoft.com contributor guides
• Post your question in the Learn support channel

[prkana]

@normesta I appreciate your support and guidance. Kindly review my justifications.

Question - what motivates the introduction of a SAS section here. To keep things simple and consistent, all examples exclude the token. We have a section in each article which states that. We also have a section in the AzCopy overview which shows an example of using SAS should folks need to. In general, SAS is not the preferred method of auth. That is why we avoid promoting it in examples. If you have some specific business need for including a section here for SAS, feel free. I plan to sweep through this content a bit later in the year and do a better job driving eyeballs to our guidance about SAS so that we don't have to include article-specific SAS examples.

Answer I have encountered multiple cases where I had the opportunity to work with customers using SAS, particularly when they experienced issues with AzCopy or AzCopy sync. In most scenarios, we were able to successfully mitigate these issues when customers used SAS. Customers also reported feeling more comfortable using SAS, especially during operations like AzCopy copy/sync from on-premises, intranet-based AzCopy, or copy/sync from their local machines.

Providing at least one example on this page would make the process more convenient for customers and would also be beneficial for support engineers.

[prkana]

The necessary response has been provided. Please share any further suggestions.

[v-dirichards]

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

Thanks!

[normesta]

#sign-off

[normesta]

@normesta I appreciate your support and guidance. Kindly review my justifications.

Question - what motivates the introduction of a SAS section here. To keep things simple and consistent, all examples exclude the token. We have a section in each article which states that. We also have a section in the AzCopy overview which shows an example of using SAS should folks need to. In general, SAS is not the preferred method of auth. That is why we avoid promoting it in examples. If you have some specific business need for including a section here for SAS, feel free. I plan to sweep through this content a bit later in the year and do a better job driving eyeballs to our guidance about SAS so that we don't have to include article-specific SAS examples.

Answer I have encountered multiple cases where I had the opportunity to work with customers using SAS, particularly when they experienced issues with AzCopy or AzCopy sync. In most scenarios, we were able to successfully mitigate these issues when customers used SAS. Customers also reported feeling more comfortable using SAS, especially during operations like AzCopy copy/sync from on-premises, intranet-based AzCopy, or copy/sync from their local machines.

Providing at least one example on this page would make the process more convenient for customers and would also be beneficial for support engineers.

Sounds good. Thank you!

[learn-build-service-prod]

Learn Build status updates of commit 5abde73:

⚠️ Validation status: warnings

File	Status	Preview URL	Details
articles/storage/common/storage-use-azcopy-blobs-synchronize.md	⚠️Warning		Details

articles/storage/common/storage-use-azcopy-blobs-synchronize.md

• Line 128, Column 56: [Warning: hard-coded-locale - See documentation] Link 'https://azure.microsoft.com/en-us/products/storage/storage-explorer' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

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.

[learn-build-service-prod]

Learn Build status updates of commit 1685caa:

✅ Validation status: passed

File	Status	Preview URL	Details
articles/storage/common/storage-use-azcopy-blobs-synchronize.md	✅Succeeded

For more details, please refer to the build report.