1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.
  2. Anuncie Aqui
    Anuncie aqui você Também: fdantas@4each.com.br

Azure deploy Error 403 - Deployment provider VSTSRM vs VSO

Discussão em 'Angular' iniciado por Silver Origami, Maio 30, 2025.

  1. Azure Angular Frontend Deploy

    I'm trying to deploy an application to Azure and I have the error:

    Error Code: ERROR_COULD_NOT_CONNECT_TO_REMOTESVC

    and

    Error: Ip Forbidden (CODE: 403)

    This is a new project, connected to a new App Service but running on the same machine as the old project that runs without errors and which I was referring to when setting up the new one. The only difference I noticed is the deployment provider. On the old machine it's VSTSRM, and on the new one it's VSO. But I don't even know how to change it because it is set automatically when setting the deployment.

    My piplenine yaml:

    trigger:
    - main # Define the branch to trigger the pipeline on

    pool:
    vmImage: 'windows-latest' # Use the latest windows agent

    variables:
    # Define your environment-specific variables here
    buildConfiguration: 'production'

    steps:
    - script: |
    npm install
    npm run build-prod
    displayName: 'Build Angular App'

    - task: CopyFiles@2
    inputs:
    targetFolder: '$(Build.ArtifactStagingDirectory)'

    - task: PublishBuildArtifacts@1
    displayName: 'Publish Artifact: drop'
    inputs:
    PathtoPublish: '$(build.artifactstagingdirectory)'

    Continue reading...

Compartilhe esta Página