Skip to content

fix: remove public npm registry calls for network isolation compliance#3590

Closed
ramsessanchez wants to merge 2 commits intomainfrom
fix/npm-network-isolation-compliance
Closed

fix: remove public npm registry calls for network isolation compliance#3590
ramsessanchez wants to merge 2 commits intomainfrom
fix/npm-network-isolation-compliance

Conversation

@ramsessanchez
Copy link
Copy Markdown
Contributor

Summary

The SDK release pipeline has been failing because outbound calls to the public npm registry (
egistry.npmjs.org) are blocked by network isolation policies.

Changes

.azure-pipelines/sdk-release.yml\

  • Changed
    etworkIsolationPolicy\ from \Permissive\ to \Restricted\ to comply with org-level network isolation policies.

.azure-pipelines/common-templates/install-tools.yml\

  • Added \customRegistry: useNpmrc\ to all three \Npm@1\ tasks (AutoRest, AutorestCore, Rush) so they explicitly route through the private Azure Artifacts feed configured by \Configure-PrivateNpmFeed.ps1, instead of falling back to the public npm registry.

Context

The \Configure-PrivateNpmFeed.ps1\ script and
pmAuthenticate@0\ steps were already correctly setting up and authenticating the private feed — the gap was that the \Npm@1\ tasks were not instructed to use it via \customRegistry: useNpmrc.

- Change networkIsolationPolicy from Permissive to Restricted in sdk-release.yml
- Add customRegistry: useNpmrc to all Npm@1 tasks in install-tools.yml so
  AutoRest, AutorestCore, and Rush installs route through the private
  Azure Artifacts feed instead of the public npm registry

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@ramsessanchez ramsessanchez requested a review from a team as a code owner April 23, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant