Error when using -FetchDnsRecordsFromAzureSubscription in Cloudshell

Describe the bug When executing .\Get-DanglingDnsRecords.ps1 -FetchDnsRecordsFromAzureSubscription in CloudShell execution fails with the error: Import-Module: Line | 13 | … Import-Module -name $module -Scope Local -Force | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Assembly with same name is already loaded

Reproduce Steps to reproduce the behavior:

1. Open CloudShell in Azure Portal
2. Execute the following command in CloudShell Invoke-WebRequest -Uri "https://raw.githubusercontent.com/Azure/Azure-Network-Security/master/Cross%20Product/Find%20Dangling%20DNS%20Records/Get-DanglingDnsRecords.ps1" -OutFile "Get-DanglingDnsRecords.ps1"
3. Execute the following command in CloudShell .\Get-DanglingDnsRecords.ps1 -FetchDnsRecordsFromAzureSubscription
4. See error: Import-Module: Line | 13 | … Import-Module -name $module -Scope Local -Force | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | Assembly with same name is already loaded

Expected behavior A list of dangling CNAME records for the subscription listed.

Environment- if applicable Azure portal CloudShell

[LarsHolte]

Same issue here also. Workaround in the cloud shell is to replace L373 with $AZModules = ('Az.Dns') as the Az.Accounts module already is loaded

[Arun-Mudiraj]

Thanks for sharing the details, I see there are 2 version of Az.Accounts loaded Script 2.2.1 Az.Accounts (version loaded in memory) Script 2.2.2 Az.Accounts (version present in modules)

When the script tries to load the latest module it fails with the error, as another version of the module is currently loaded. Can you please wrap the lined in the code Import-Module -name $module -Scope Local -Force to below, and let us know the result.

if (-not (Get-Module -Name $module)) { Import-Module -name $module -Scope Local -Force }

Will update code accordingly.