Category: Exchange/Office 365

Due to the rapid changes of mobile device OS and Office 365 specifications, Microsoft release a communication to inform us to update your Apple devices to a new iOS version to have a better Outlook for iOS compatibility:

With the release of iOS 11, we want to remind you that Outlook for iOS is supported only in the last two releases of iOS. This means new app updates to Outlook will now only be supported on devices with iOS 10 or iOS 11.
How does this affect me?
You are receiving this message because our reporting indicates one or more users in your organization are using Outlook for iOS on iOS 9.
Devices with iOS 9 are no longer be supported. While older versions of Outlook will still work on devices running iOS 9, these devices will not get new app updates after build 2.48. Users can expect a degraded experience of the Outlook for iOS app over time, if they do not stay up-to-date.
What do I need to do to prepare for this change?
We encourage you to stay up-to-date to maintain the best Office 365 experience.

Often happen that a customer has more then one email domain in his On-Premises infrastructure. This should be considered when you plan to deploy AD FS Services to enable Single Sign-On with Office 365.
With the newest version of Azure AD Connect, steps to federate On Premises AD DS with Azure AD is fully automated though it assumes that the domain specified during the wizard steps is the only one domain you want to federate (If you need an overview of Azure AD Connect step-by-step configuration, please refer to Microsoft Docs here).

This will cause disruption of users login to Office 365 apps. To solve this situation you need to change the federation mode configured by the wizard manually using Powershell and set it to a Multi Domain federation. Read More

Sometime happen strange things. In the past days I faced a really weird issue with a migration from Exchange 2010 to Exchange 2016 for a customer.

I was at the point in which Exchange 2016 should be inserted as frontend server for all communications: all the load balancer Kemp (LAN and DMZ) was switched and all the checks was ok.
SMTP, ActiveSync, Outlook Anywhere, Autodiscover ECP and OWA was ok and the authentication between servers works fine. SMTP mail flow inbound and outbound moved to brand new servers. I also tested some mailbox migration and access to OWA and ECP.

That’s was fine, mailbox migration time! Customer’s IT responsible start to migrate some test mailbox before start a massive migration and after a couple of day they had problem to access to Outlook Web Access. It’s my turn to check which is the problem.

Sometimes happen that Exchange Database Content Index switch from Healthy to Fail. The first behaviors the users experiences is a fail on Search in their Outlook client (even if on Premises and Outlook Web Access).

Usually this fail go unnoticed when everything else is working fine however they will eventually begin to cause problems if you have a Database Availability Group (DAG) in place, for example by preventing database switchovers, thus it’s a good practice to monitor the status.
To achieve monitoring, I’m using a specific powershell sensor when customers have active Monitoring Services (in my case Peassler PRTG), otherwise here you could download an usefull script provided by Paul Cunningham to use as your needs. Read More