-
Notifications
You must be signed in to change notification settings - Fork 4.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Provisioning with a Service Principal. #962
Comments
@pamelafox - Prob good idea to add a param to main.bicep that allows people to specify principalId type |
Yep, seems like a good idea, AZD_USER_TYPE or some such? I assume we can't detect it programmatically from the principalId. |
AZURE_PRINCIPAL_TYPE |
@pamelafox @jongio Is this limited to this repo or is there a broader AZD issue that needs to be addressed? |
I think this particular issue can be resolved within this repo, though I haven't given it a go myself to be 100% certain. |
Any solution for the issue? I run azd up in github workflow meet the same issue. Any solution instead of change the main.bicep? and Why it's different from run azd up in local? |
…s#962) Co-authored-by: Ian Seabock (Centific Technologies Inc) <v-ianseabock@microsoft.com>
I provisioned with a service principal because my environment does not allow browser authentication. I changed main.bicep because of some errors, is there a problem with this change? Search form the app seems to work. Thanks in advance.
This issue is for a: (mark with an
x
)Minimal steps to reproduce
Created the service principal.
login
provision
Changed main.bicep as follows:
Any log messages given by the failure
Expected/desired behavior
OS and Version?
azd version?
Versions
Mention any other details that might be useful
The text was updated successfully, but these errors were encountered: