Always confirm tenant for connect-graph, confirm Autopilot config exists. #22
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I encountered times when I ran New-ClientVm and I was already authenticated to Tenant A via Connect-Graph but I wanted to create a ClientVm for Tenant B and I also need to create a new Autopilot config for Tenant B. The Connect-Graph step seems to get skipped and I am not then able to authenticate to Tenant B and no Autopilot config is created.
Adding a -ForceInteractive to Connect-Graph solved this in my trial runs by requiring me to select which account to use.
Additionally I added a throw in New-ClientVM.ps1 in case the Autopilot config is not found.
My apologies if I am missed something. This is my first ever pull request.