Skip to content

docs: Update LocalDeployment.md to include Azure Cosmos DB and Azure OpenAI authorization (RBACs)#33

Closed
sjuratov wants to merge 1 commit intomicrosoft:mainfrom
sjuratov:demo
Closed

docs: Update LocalDeployment.md to include Azure Cosmos DB and Azure OpenAI authorization (RBACs)#33
sjuratov wants to merge 1 commit intomicrosoft:mainfrom
sjuratov:demo

Conversation

@sjuratov
Copy link

Purpose

  • Allow AAD Entra user to run accelerator locally

Does this introduce a breaking change?

  • Yes
  • No

How to Test

  • Use instructions in documentation to authorize access to Azure Cosmos DB and Azure OpenAI

What to Check

Verify that the following are valid

  • AAD Entra user should be able to run accelerator after following the instructions in the documentation

Other Information

@Roopan-Microsoft
Copy link
Collaborator

Roopan-Microsoft commented Jan 16, 2025

Hi @sjuratov

Just want to check if you have used macae-dev.bicep as per documentation from the local deployment? Because it has the code to assign the role but macae.bicep doesn't have it.

@sjuratov
Copy link
Author

Hi @Roopan-Microsoft , I have used Deploy to Azure button.

I see now that you have step #4 "Deploy the Bicep template" in local deployment guide but I think it doesn't hurt if you always assign these RBACs, regardless of how you deploy infra.

@Roopan-Microsoft
Copy link
Collaborator

Hi @Roopan-Microsoft , I have used Deploy to Azure button.

I see now that you have step #4 "Deploy the Bicep template" in local deployment guide but I think it doesn't hurt if you always assign these RBACs, regardless of how you deploy infra.

Hey @sjuratov - We have updated the documentation to have those steps to be executed (Cosmos & OpenAI) role if we are using other than macae-dev.bicep. So we got a suggestion to avoid providing roles, if user needed any specific they can add themselves.

image

@sjuratov
Copy link
Author

Hi @Roopan-Microsoft , that sounds good to me.

@Roopan-Microsoft
Copy link
Collaborator

Thanks @sjuratov - Closing this PR for now as we already handled it.

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.

2 participants