Probably encounter most often (based on a limited test). The default profile name is Outlook, and it’s the one that you’ll Each profile has its own settings, including $UserProperties = Get-AzureADUser -ObjectId $UserId # Retrieve the properties of the user from Azure Active Directory $UserAccount = Get-ItemProperty -Path HKCU:\Software\Microsoft\Office\Outlook\Settings -Name Accounts | Select -ExpandProperty Accounts I then use the user principal name to fetch account properties from Azure Active Directory: My solution is to fetch the accounts information and parse out the user principal name. The first issue was to find out from the registry which Azure Active Directory account is used with Outlook. Outlook and the SystemĪs noted in my other article, Outlook for Windows stores information about its settings in the system registry.
So I decided to explore the topic by putting together my own version. To support Office ProPlus (click to run) or not using Azure Active Directory. Scripts I met were old and suffered from one problem or another, like failing As it turns out, there’s quite a few methods suggested in various blogs and articles, mostly on the theme of how to use information from Active Directory into signatures ( here’s an example). After finishing my article about Microsoft developing cloud signatures for Outlook, I decided to look at what’s involved with updating an Outlook signature with PowerShell.
0 kommentar(er)
