Skip to content
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

fix: use subscription api for tenant id retrieving #3359

Merged
merged 3 commits into from
Jun 9, 2020
Merged

Conversation

zidaneymar
Copy link
Contributor

@zidaneymar zidaneymar commented Jun 9, 2020

Description

Currently the provision script is using 'tenant list api' which could list all tenants for selection.
If user provide the subscription id, we should use the tenant id associated with the specific subscription.
So use this api instead.
https://docs.microsoft.com/en-us/rest/api/resources/subscriptions/get

Task Item

fixes #3313
fixes #3324

Screenshots

@coveralls
Copy link

coveralls commented Jun 9, 2020

Coverage Status

Coverage remained the same at 43.084% when pulling eb3c6cf on qika/tenant into 40a0f97 on master.

@cwhitten cwhitten merged commit 517a71c into master Jun 9, 2020
@cwhitten cwhitten deleted the qika/tenant branch June 9, 2020 17:58
@cwhitten cwhitten mentioned this pull request Jul 8, 2020
lei9444 pushed a commit to lei9444/BotFramework-Composer-1 that referenced this pull request Jun 15, 2021
Co-authored-by: Chris Whitten <christopher.whitten@microsoft.com>
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.

"User was not found" While following publish steps after Azure login Can't publish my bot to azure
3 participants