What was helpful was this Doc regarding Azure PowerShell context objects.
Not at all helpful in this context (see what I did there?). No matter what permutation I used of these search terms, the limited results I did find were related to API calls or application errors. On hitting this error I did what most seasoned IT Professionals would do - I searched the internet for the phrase "failed to acquire token silently as no token was found in the cache the refresh token had expired due to inactivity". In this case, with none selected, I issued the next command "Set-AzContext" and provided the -SubscriptionID that I wanted the commands to act against, only. Usually one is picked up by default but you can use the same process to switch to a different subscription or tenant if needed.
This account has access to multiple subscriptions in a single tenant, so before we start issuing commands, we need to set the context. This was a slightly tricky question, as you may not be able to tell that I haven't blacked out the SubscriptionName or TenantID for security reasons.
#Mac outlook 2016 server for account returned the error [authenticationfailed] password#
The login process seemed to then authorize my username and password without error, but there was something strange in what was returned (see if you can spot it, below): In PowerShell, I ran the "Connect-AzAccount" command, visited the website and entered the provided (redacted) code. So what happens if you hit an error with that very first step? The first step is connecting PowerShell to your tenant and subscription with valid credentials, using the "Connect-AzAccount" command.
PowerShell provides an effective way to run queries or actions at scale, whether that's against Azure resources, Azure Active Directory identities or Office 365 environments (including Exchange Online, SharePoint Online and Microsoft Teams).