Issues creating new PrivateLink Connections in Azure

This incident has been resolved.

We rolled out mitigations across the affected Azure regions. We have confirmations that the mitigations we've rolled out so far have been successful. We are continuing monitoring for further issues

We are continuing to monitor for any further issues.

We rolled out mitigations across the affected Azure regions. We have confirmations that the mitigations we've rolled out so far have been successful. We are continuing monitoring for further issues

We are continuing to rollout mitigations across the affected Azure regions. We have confirmations that the mitigations we've rolled out so far have been successful. Once changes have been rolled out across all the regions we will return with an update.

We've found a solution and are continuing to mitigate the issue across Azure regions. We will continue to monitor our solution across the platform and will post an update within the next hour.

The issue has been identified as configuration change on Azure's side. Our team is actively working on mitigating the issue and will post an update in an hour.

We have received reports from users where they cannot create new PrivateLink connections in Azure regions of Elastic Cloud. Existing PrivateLink connections continue to operate as expected.
Our team is investigating the issue and will post an update in 1 hour.