search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.09k stars 21.13k forks source link

Source IP ranges not valid for Azure Storage Firewall #15125

Closed DonPetry-EY closed 5 years ago

DonPetry-EY commented 5 years ago

The Source IP ranges listed per region for LogicApps does not work with Azure Storage Firewall. In fact, Azure Storage Firewall is not currently compatible, supported or functional when used in conjunction with LogicApps. A LogicApp is not able to reach Azure Storage in the same region when Azure Storage Firewall is enabled even when source IP whitelisting is configured per this article.

Document Details

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

BryanTrach-MSFT commented 5 years ago

@DonPetry-EY Thanks for the feedback! We are currently investigating and will update you shortly.

mike-urnun-msft commented 5 years ago

@ecfan We may have to add a callout text communicating this limitation.

mike-urnun-msft commented 5 years ago

Hi @DonPetry-EY Thanks again for your feedback. Please upvote the existing feature request on this issue at Azure UserVoice for product team to review and consider for future roadmap.

We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

DonPetry-EY commented 5 years ago

Hi Mike,

I don't see any mention of this limitation in the article. Thanks for the feature request, I've voted it up.

Given that this article specifically mentions Source IP Firewall configurations required for LogicApps, doesn't this at least warrant a mention such as "Firewall enabled Storage Accounts are not compatible with LogicApps. To connect a LogicApp to a Storage Account, ensure the Firewall setting is not enabled".

Otherwise, how would someone know of this deficiency?

mike-urnun-msft commented 5 years ago

@DonPetry-EY Agreed! I've reached out internally and we're reviewing.

ecfan commented 5 years ago

Thanks @DonPetry-EY + @mike-urnun-msft! I created a work item to address this limitation.

please-close

mike-urnun-msft commented 5 years ago

Hey @DonPetry-EY As per your feedback, we'll now proceed to update this documentation to communicate this detail better. This issue will remain in closed state as we have created a work item internally to track this issue (as per Esther's comment above.) Thank you again for helping us drive improvements toward MS docs, and we certainly appreciate this contribution. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

DonPetry-EY commented 5 years ago

Thanks Mike… I really appreciate the response and approach. Nicely done!

---kind regards,

[cid:image001.png@01CF54AE.93410BB0]

Don Petry | Architecture, Design & Engineering Lead, Client Technology Platforms: Data & Analytics | EY Technology – Client Technology

Ernst & Young LLPhttp://www.ey.com/

1105 Lakewood Parkway, Suite 200, Alpharetta, GA 30009, USA

Office: +1 470 268-1639 | Mobile: +1 678 898-0127 | Fax: +1 404 817-4301

don.petry@ey.commailto:don.petry@ey.com

From: Mike Urnun [mailto:notifications@github.com] Sent: Wednesday, September 26, 2018 2:32 PM To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: Don Petry don.petry@ey.com; Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] Source IP ranges not valid for Azure Storage Firewall (#15125)

Hey @DonPetry-EYhttps://github.com/DonPetry-EY As per your feedback, we'll now proceed to update this documentation to communicate this detail better. This issue will remain in closed state as we have created a work item internally as per Esther's comment above. Thank you again for helping us drive improvements toward MS docs, and we certainly appreciate this contribution. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/15125#issuecomment-424822950, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AivEbtyB80IwF3bGDzyYYviBChKPMa0bks5ue8gogaJpZM4WsrKc.

Any tax advice in this e-mail should be considered in the context of the tax services we are providing to you. Preliminary tax advice should not be relied upon and may be insufficient for penalty protection.

The information contained in this message may be privileged and confidential and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by replying to the message and deleting it from your computer.

Notice required by law: This e-mail may constitute an advertisement or solicitation under U.S. law, if its primary purpose is to advertise or promote a commercial product or service. You may choose not to receive advertising and promotional messages from Ernst & Young LLP (except for EY Client Portal and the ey.com website, which track e-mail preferences through a separate process) at this e-mail address by forwarding this message to no-more-mail@ey.com. If you do so, the sender of this message will be notified promptly. Our principal postal address is 5 Times Square, New York, NY 10036. Thank you. Ernst & Young LLP

ecfan commented 5 years ago

@DonPetry-EY We added info to this article, which should help and is queued up for publishing. Feel free to check back after 4 PM or tomorrow, and let us know whether the update helps. Thanks!