Azure-docs: Private IP ranges incorrect

Created on 18 Sep 2018 · 6Comments · Source: MicrosoftDocs/azure-docs

172.16.* should be 172.16-31.*

Document Details

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

ID: 45d20da7-23ff-7f4b-6689-be40e3b55028
Version Independent ID: 20d481b8-80bc-8249-7196-7d09834f61c2
Content: VNET Service Endpoints for Azure Key Vault
Content Source: articles/key-vault/key-vault-overview-vnet-service-endpoints.md
Service: key-vault
GitHub Login: @amitbapat
Microsoft Alias: ambapat

Pri2 assigned-to-author doc-bug key-vaulsvc triaged

Source

aarsan

Most helpful comment

Currently, it does not look as though DevOps is considered a Trusted Microsoft Service in regards to KeyVault. Is this true and if so, is it on the Roadmap to be added as a trusted service? My customer wants to implement Firewall and VNet service endpoints on their Keyvault, but they don't want to break DevOps access to KeyVault. Please advise. Thanks.

gusgallows on 9 Aug 2019

👍2

All 6 comments

@aarsan
Thanks for your feedback! We will investigate and update as appropriate.

MarileeTurscak-MSFT on 18 Sep 2018

@aarsan Thanks for the feedback ! I have assigned this issue to content author to investigate and update the document as appropriate.

SaurabhSharma-MSFT on 18 Sep 2018

👍1

gusgallows on 9 Aug 2019

👍2

@gusgallows - yes. We use CircleCI, and I thought about switching to Azure Devops just for this reason. Can't believe it's not on that list!

robertlagrant on 28 Dec 2019

The original issue in the thread regarding IP address range has been resolved.
The Azure DevOps team is aware of the trusted services list issue and are working to resolve. The current workaround is to whitelist the DevOps IP address ranges in the key vault firewall.