[Bug]: "[TenantError] Unable to get tenant information when external user is used to authenticate"

[olivierdumon]

What happened?

Error message after authentification :
[TenantError] Unable to get tenant information: Exception setting "tenantName": "The property 'tenantName' cannot be found on this object. Verify that the property exists and can be set."
At C:\Program Files\WindowsPowerShell\Modules\monkey365\0.95.5\core\tenant\Get-TenantInformation.ps1:153 char:13
+             throw ("[TenantError] {0}: {1}" -f "Unable to get tenant  ...
+             ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo          : OperationStopped: ([TenantError] U...nd can be set.":String) [], RuntimeException
+ FullyQualifiedErrorId : [TenantError] Unable to get tenant information: Exception setting "tenantName": "The property 'tenantName' cannot be found on this object. Verify that the property exists and can be set."

How to reproduce it
Steps to reproduce the behavior:

1. What command are you running?

Invoke-Monkey365  -Instance  Microsoft365  -Collect AdminPortal,ExchangeOnline,MicrosoftTeams,Purview,SharepointOnline  -ScanSites https://xxxxxxx.sharepoint.com -IncludeEntraID  -ForceMSALDesktop -Verbose  -InformationAction Continue -Compress  -ExportTo HTML

2. See error

Expected behavior
HTML result report

From where are you running Monkey365?
Please, complete the following information:

• Resource: Workstation
• OS: Windows 11 Pro 24H2
• PowerShell Version : 5.1.26100.4202
• Monkey365 Version: 0.95.5

Additional context
The login used has admin access to several tenants.

[silverhack]

Hi @olivierdumon thanks for submitting this!

That's a really weird issue, because the tenantName property is created before any execution is done.

I'll investigate it more in depth and I will let you know soon.

Thanks,

[silverhack]

Hi @olivierdumon I've updated the develop branch and I'll publish a new version (0.95.6) by today. Some logic was added to get info from internal variables, and I believe it's now sorted. Could you please check it again and do let me know if it works for you?

Thanks in advance,

[silverhack]

Hi @olivierdumon, a new version was already published.

Thanks,

[olivierdumon]

Hi @silverhack
Thanks for your actions and sorry for the delay.
I did a new test with the latest version but I have the same problem.

As already mentioned, the account used has admin rights on several tenants.
I don't have this kind of problem when the account can connect to only one tenant

Thanks
Good day
Olivier

[silverhack]

Hey @olivierdumon thanks for letting me know. For your specific use-case, in which an admin has several rights to different tenants the best way would be to pass the -TenantId <your_tenant_id> to monkey365

[silverhack]

Hi @olivierdumon I will set up a lab with multiple tenants per user and I will try to replicate your issue. I hope to get back to you shortly with more information.

Cheers