Those who have worked with hybrid environments where they needed resources located in the on-premises network to resolve Azure resources’ private endpoints would remember that there wasn’t a great way to do this before Azure DNS Private Resolver was available. I remember having to create
Problem A colleague of mine recently asked me to help troubleshoot an issue with an Azure Storage Account that has Hierarchical Namespace enabled, which is essentially an Azure Data Lake, where any attempts to create a folder would fail: The error message presented was generic
I’ve had the opportunity to work on several projects over the past year to design disaster recovery to recover from one Azure region to another. One of the most common topics that comes up is how to handle storage accounts that are accessed through private
Problem You attempt to configure a private endpoint for an API Management service but unable to select any Target sub-resource in the Resource configuration: The value must not be empty. No supported sub-resources No available items. Solution For this environment, the issue was that the
