Skip to content

Conversation

Prasanjeet-Microsoft
Copy link
Contributor

Purpose

  • This PR enables the assignment of System Assigned Managed Identity (SAMI) to an existing Azure AI Foundry project when it is reused in deployments. This ensures that role-based access can be granted even when the AI project already exists.
  • Additionally, it introduces a README section that documents how to reuse an existing Azure AI Foundry project. This includes step-by-step instructions for locating the project in the Azure Portal, extracting its Resource ID, and configuring it via azd env set.

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Get the code
git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

What to Check

Verify that the following are valid:

  • The system-assigned managed identity is successfully enabled for reused (existing) AI Foundry projects.

  • The identity appears in the Azure Portal under the Identity section of the AI project.

  • No new project is created when reusing an existing one.

  • Role assignments dependent on the system-assigned identity work correctly.

  • Output values (name, resource ID, API endpoint) are accurate for both new and existing projects.

  • The behavior for creating a new AI project remains unchanged and unaffected.

  • The reuse guide in the README:

    • Follows the format of existing documentation (e.g., Log Analytics workspace reuse)
    • Accurately describes how to navigate Azure Portal and locate the AI Foundry project's Resource ID
    • Uses the correct azd command to configure the environment variable
    • Aligns with the expected behavior in single-project Foundry services

…projects and add documentation for reusing existing Azure AI Foundry project
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

invalid This doesn't seem right

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant