search

pnp / provision-assist-m365

Provision Assist is a request and provisioning solution for Teams, Groups, SPO Sites and Viva Engage Communities in Microsoft 365. It can be used as part of a Copilot for Microsoft 365 deployment.
MIT License
62 stars 9 forks source link

Resource Group Exist then Not Found #72

Open oneslade opened 7 months ago

oneslade commented 7 months ago

Description

Running the Deploy.ps1, the resource Group is identified as existing. Next step Deploying key vault and automation account the Resource group could not be found

resource group issue

Steps to reproduce

1.Ran Deploy.ps1 2.Created SharePoint Site 3.Confirmed provided Resource Group Exist - Y 4.Screen confirms ResourceGroupName 5.Created resource group 6.Deploying Azure resources 7.Deploying key vault and automation account 8 Error message as attached deploy.ps1 stops

Expected results

The resourcegroup to be updated with the relevant objects

Actual Results

error message as attached

resource group issue

Solution component

Deployment Script

Operating system (environment)

Windows

Additional Info

No response

alexc-MSFT commented 7 months ago

@oneslade can you double check that when you ran the script you logged into the correct tenant when it was logging into the Azure CLI? It might be that it's looking for that resource group in the wrong tenant (the resource group check actually uses a different module to the creation of resources). Thanks

KashifMajeed24 commented 5 months ago

I'm getting the same error. Was there any fix to this? I'm logged into correct tenant.

KashifMajeed24 commented 5 months ago

@alexc-MSFT / @oneslade did you guys find any solution to this problem? I can't figure out what could be wrong...

alexc-MSFT commented 2 weeks ago

@oneslade @KashifMajeed24 I'm not sure if this is helpful but we have made lots of changes to the deployment script as part of recent updates and have transitioned to PowerShell 7 where we have tweaked the CLI login, it should now ask you to select the subscription when running the script and this should eliminate this error.