Yes. Covered in https://practical365.com/azure-automation-managed-identity-exo/.

This is the problem with covering a cloud service like Microsoft 365 which changes all the time. I’ll update that post, but when you have thousands of posts to manage, keeping them all updated is a horrendous task. Which is why we have the Office 365 for IT Pros eBook. https://gum.co/O365IT/

It appears that microsoft has updated the exchange module to allow for Managed identities to be used to connect to exchange online:

https://learn.microsoft.com/en-us/powershell/exchange/connect-exo-powershell-managed-identity?view=exchange-ps

According to the Get-Command cmdlet, Update-ModuleManifest is part of the PowerShellGet module. You need that module to update from the PowerShell gallery: https://learn.microsoft.com/en-us/powershell/scripting/gallery/installing-psget?view=powershell-7.3

The Set-AzAutomationVariable https://learn.microsoft.com/en-us/powershell/module/az.automation/set-azautomationvariable?view=azps-9.1.0 cmdlet is available to set variables for an automation account. You’d need to do this before running a script. the Get-AzAutomationVariable cmdlet https://learn.microsoft.com/en-us/powershell/module/az.automation/get-azautomationvariable?view=azps-9.1.0 retrieves the variable value when the script runs.

Interesting. Get-User works OK interactively but you’ve found that it doesn’t when executed by an Azure Automation runbook? If so, that’s definitely a bug. But Get-User is a very old cmdlet and Get-MgUser is probably a better bet going forward…

Its the Get-User cmdlet. I may have to look at using Get-MgUser from the graph api.

Do you mean Get-MgUser? If so, Get-MgUser -All returns all available user accounts.

If you mean the Get-User cmdlet, an error after a certain number of results sounds like a bug and I would report it as such to Microsoft (or use Get-MgUser!)