The hosting venue has changed to serve you better.
This morning, looking for an answer to something, I stumbled across a question that seemed easy enough to fix: Is it possible to export the GAL from Outlook if I don’t have access to a server?
Yes, yes it is. Since we have the Power of Grayskul–err, PowerShell, at our disposal, we can manipulate Outlook to return this data to us. … [ Continue reading ]
So, imagine this:
The security team comes to you and asks you for a report on how people are accessing Exchange Online services–browser, mobile, Outlook client. In the olden days of Exchange on-premises, you could look at the IIS logs to check browser traffic. … [ Continue reading ]
Today, one of my consultant peers posed a problem to me: a customer wanted to import all PSTs into Office 365 archives, but in order to do that, had to disconnect them from the user’s default Outlook profile.
Fortunately, you can expose a number of methods and properties from the Outlook ComObject inside PowerShell, so this wasn’t terribly difficult (although, I’m still trying to figure out how to do this against all Outlook profiles configured).… [ Continue reading ]
From time to time, we update the URLs and IP addresses that our services use. This happens as a normal course of business (deploying new services, adding new capacity in datacenters or regions). If your organization is trying to filter network traffic, you need to make sure you are allowing your users to these services. … [ Continue reading ]
In case you ever need to configure Outlook for an Office 365 tenant that *does not* have AutoDiscover records published, here is how to do it.
1. Log into PowerShell for tenant and run the following command:
Get-Recipient | Select-Object Identity,Mail,ExchangeGuid | Export-Csv .\recipientlist.csv