Access private Azure storage account via Azure devops deployment

Alex Izrailov 6 Reputation points
2022-03-02T13:48:17.297+00:00

I have an Azure storage account which is closed to public networks and only available to selected networks that we set to work against this storage account. One problem that we encountered is that the storage account is also used by Azure function app and it has a cicd pipeline with Azure devops. The issue is that when the storage account is not accessible via public routing the cicd release pipeline crashes. I can't understand how to enable it. Any ideas ? Thanks ahead

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,747 questions
Azure Blob Storage
Azure Blob Storage
An Azure service that stores unstructured data in the cloud as blobs.
2,487 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sumarigo-MSFT 44,081 Reputation points Microsoft Employee
    2022-03-03T06:54:46.11+00:00

    @Alex Izrailov Welcome to Microsoft Q&A Forum, Thank you for posting your query here!

    I'd recommend to post your DevOps query, in Developer Community to receive a focused and immediate assistance from the right set of experts. These forum community members could provide their expert guidance on your scenario based on their experience. Thanks.

    Additional information: In mean while you refer to the suggestion mentioned in this thread Access azure storage account from pipeline agent which may provide some idea on your scenario.

    There is a discussion in GitHub on Azure pipeline IP host ranges AzureDevops

    Use private endpoints for Azure Storage

    Please let us know if you have any further queries. I’m happy to assist you further.

    ----------

    Please do not forget to 179405-screenshot-2021-12-10-121802.png and 179406-image.png wherever the information provided helps you, this can be beneficial to other community members.

    0 comments No comments