Skip to content

Allow private VNet integration through private endpoint #10

Description

@MadMarc-gh

Component

Portal

Problem or motivation

Useful Azure resources can have public network access disabled, preventing Automation workflows to access them (e.g. private Foundry agents).

Proposed solution

Allow the Automation Project to have its own private endpoints.

Alternatives considered

No response

Additional context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions