Use Azure Storage Explorer rather than B2CAzureStorageCLient

[WhippsP]

Could I suggest a change to use Azure Storage Explorer rather than a custom built tool. This tool also allows you to configure CORS.
https://azure.microsoft.com/en-gb/features/storage-explorer/

---

Document details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 36c209d9-c15f-87a4-a7ee-bb2bd3416961
• Version Independent ID: 2f76d983-a940-fa5f-abe0-4c851e377608
• Content
• Content Source
• Service: active-directory-b2c

[amanarneja]

@WhippsP Thanks for your suggestion, we are investigating and will get back to you.

[jlsfernandez]

Hello

any news about this?

[MohitGargMSFT]

@swkrish Can you please check and update on it soon?

@jlsfernandez Apologies for delay in response here. I will try to reach out to author offline as well to get an update. Thanks for your patience.

[rojasja]

Hello @WhippsP,

I am from the Azure AD B2C team and can take a close look at this. Are you saying that if we use Azure Storage explorer, the CORS tool will not be necessary?

If so... excellent.

Can you point me to the documentation for this... How would a b2c user upload the HTML, configure coors, and then enable the storage to be available publicly?

https://azure.microsoft.com/en-gb/features/storage-explorer/

Thank you!

[WhippsP]

Jose, Unfortunately I cant seem to find the official documentation however the steps are; Right Clieck on the Blob Container and select “Configure CORS Settings…” [cid:image006.jpg@01D3C022.57ED31E0] Then add login.msol [cid:image007.jpg@01D3C022.57ED31E0] As far as uploading the Files I just drag and drop however there is an upload button when the container is selected [cid:image005.png@01D3C021.59E526C0] To enable public access you just right mouse click on the container and select “Set Public Access Level…” [cid:image008.png@01D3C022.24C86410] And Select Public read access for blobs only [cid:image009.png@01D3C022.57ED31E0] Thanks Phil Whipps Identity & Access Management Consultant UNIFY <http://www.unifysolutions.net/> Solutions Pty Ltd<http://www.unifysolutions.net/> Identity and Access Management Specialists Website: http://www.unifysolutions.net/ Office: +61 1300 889 519 Mobile: +61 422 361 545 From: Jose Rojas [mailto:notifications@github.com] Sent: Tuesday, 20 March 2018 3:33 AM To: MicrosoftDocs/azure-docs <azure-docs@noreply.github.com> Cc: Phil Whipps <phil.whipps@unifysolutions.net>; Mention <mention@noreply.github.com> Subject: Re: [MicrosoftDocs/azure-docs] Use Azure Storage Explorer rather than B2CAzureStorageCLient (#5082) Hello @WhippsP<https://github.com/whippsp>, I am from the Azure AD B2C team and can take a close look at this. Are you saying that if we use Azure Storage explorer, the CORS tool will not be necessary? If so... excellent. Can you point me to the documentation for this... How would a b2c user upload the HTML, configure coors, and then enable the storage to be available publicly? https://azure.microsoft.com/en-gb/features/storage-explorer/ Thank you! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<#5082 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AFNwUeYLHWuWbJ4zBWi5nkAG3eUHDUsWks5tf-vAgaJpZM4SV5kG>.

[davidmu1]

@WhippsP Thank you for bringing this to our attention. We have opened an item in our documentation backlog to have this investigated and updated. We'll respond back to you on this issue when we've done the work. For now, we'll close this GitHub issue.

#please-close