Can no longer connect to Azure with Connect-AzAccount

Mentat · October 25, 2023, 7:22pm

Product: PowerShell Universal
Version: 4.1.7

Hey PSU folks,

Today I decided to upgrade from 4.0.9 to 4.1.7, and now PSU can no longer connect to Azure using Connect-AzAccount. I keep getting the following error:

Entry point was not found. Could not find tenant id for provided tenant domain ‘x-x-x-x-x’. Please ensure that the provided service principal ‘x-x-x-x-x’ is found in the provided tenant domain.

I get this when a page runs Connect-AzAccount using a service principal.

Connect-AzAccount -TenantId $tenantId -Credential $creds_Azure -ServicePrincipal -Subscription $defaultSubscription -ErrorAction Stop

However, the exact same command works when run from the PoSh 7 shell and from VSCode .

I have 2 questions:

Is there a solution readily available?
How can I roll back a PSU installation for MSI install? I see instructions for install and upgrade on the Ironman site, but not for roll back. I backed up my UniversalAutomation folder prior to upgrade. Is it as simple as uninstalling current version, overwriting the UniversalAutomation folder with the backup, then running the MSI installer for the previous version?

I should mention that I’m running PoSh version 7.3.8 and the latest Az.Accounts module version 2.13.1.

Thanks,
Rob

Mentat · October 26, 2023, 3:52pm

Update…I restored the VM from the previous day’s image backup, and I can now connect to Azure using Connect-AzAccount with a service principal again.

Although image restore is possible for me, anyone know what the proper process is for roll back in a situation where the updated version is causing problems; using MSI for install?

Thanks,
Rob

Matt.Harris · October 27, 2023, 12:16pm

There’s a known bug for this which will be fixed in 4.2 (currently fixed in the 4.2 beta).

github.com/ironmansoftware/issues

"Entry point was not found" when using KeyVault modules

opened 12:55PM - 15 Sep 23 UTC

closed 05:46PM - 09 Oct 23 UTC

MattHarrisUltima

bug PowerShell Universal completed

### Version 4.1.0 ### Severity High ### Steps to Reproduce Following testin…g of a new environment and upgrade of a container image on an existing environment, Azure connectivity does not appear to be working as expected. The container image in question is: `ironmansoftware/universal:4.1.0-modules` In a new environment, PowerShell Universal appears to be unable to connect to an Azure Tenant via Service Principal. claiming it can not find an application ID in the given tenant. ``` [warning] The provided service principal secret or certifcate password will be included in the 'keystore.cache' file found in the user profile ( /root/.Azure ). Please ensure that this directory has appropriate protections. [error] Entry point was not found. Could not find tenant id for provided tenant domain 'xxxxxxxx-aae9-44fe-bdc4-53f76xxxxxd0'. Please ensure that the provided service principal 'xxxxxxx-4d45-4a37-be96-dfea4xxxxx71' is found in the provided tenant domain. ``` In an upgraded environment, `Get-AZContext` returns the current subscription in a tenant however `Disconnect-AZAccount` returns the following error: ``` [ERROR] Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Identity.Client.Broker.BrokerExtension.WithBrokerPreview(Microsoft.Identity.Client.PublicClientApplicationBuilder, Boolean)'. ``` A `Get-AZKeyvault` returns the following error: ``` [ERROR] Your Azure credentials have not been set up or have expired, please run Connect-AzAccount to set up your Azure credentials. Entry point was not found. ``` I can see there have been some version changes in the modules provided this may be the problem ![2023-09-15 13_54_24-PowerShell Universal — Mozilla Firefox](https://github.com/ironmansoftware/issues/assets/106333485/1697defa-59c4-41a7-994a-3b330c489ec9) : ### Expected behavior ```console Commands like `Connect-AZAccount`, `Disconnect-AZAccount`, and `Get-AZKeyvault` work as expected. ``` ### Actual behavior ```console `Disconnect-AZAccount` returns the following error: [ERROR] Method not found: 'Microsoft.Identity.Client.PublicClientApplicationBuilder Microsoft.Identity.Client.Broker.BrokerExtension.WithBrokerPreview(Microsoft.Identity.Client.PublicClientApplicationBuilder, Boolean)'. ``` A `Get-AZKeyvault` returns the following error: ``` [ERROR] Your Azure credentials have not been set up or have expired, please run Connect-AzAccount to set up your Azure credentials. Entry point was not found. ``` Reverting to 4.0.12-modules and re-running my keyvault setup commands appears to return functionality. ``` ### Additional Environment data _No response_ ### Visuals _No response_

I believe the issue was traced to an SQL client package.

I would advise you stay on your current version until 4.2 is out.

Mentat · October 31, 2023, 3:20pm

Sounds good. Thanks @Matt.Harris

Topic		Replies	Views
Issue setting up keyvault for a 4.1.1 Docker Hub image	7	186	September 21, 2023
Automation job - Certificate issuess and azure connection Universal Automation	2	519	November 30, 2020
PowerShell Universal - 3.5.5 releases	2	328	November 22, 2022
Issue connecting to AzureAD PowerShell Universal	1	338	August 18, 2021
How to Import Azure AD Module into Universal Rest API? PowerShell Universal	2	724	August 6, 2021

Can no longer connect to Azure with Connect-AzAccount

Related Topics