- The default browser/mail app selection will be reset after the restart of iOS/iPadOS. This is an iOS14 issue, Apple is aware of the issue. (Fixed today with iOS 14.0.1, check your updates)
- If the default browser is set to a browser other than Safari, Teams cannot open links. Teams is aware of the issue and is investigating.
- Apps that rely on MFMailComposeViewController will be directed to the Mail app even when the default mail app is set to a different mail app. This is an iOS14 issue, Apple is aware of the issue.
- mailto:// links will launch the Mail app if the Mail app has an account profile, even when the default mail app is set to a different mail app. This is an iOS14 issue, Apple is aware of the issue.
- Notifications previews do not show sender/subject/preview and instead show "Open Outlook to read this message" when the device is enrolled and Outlook is pinned to the management profile. The Outlook team is working with Apple to investigate the issue.
- On enrolled devices, OneDrive cannot be accessed through the FileProvider API when the app is pinned to the management profile and opening documents from managed to unmanaged apps is not allowed. The same behavior occurs with Google Drive. Apple is aware of the issue.
Microsoft will be releasing the next versions of Exchange Server, SharePoint Server, and Skype for Business Server the second half of 2021. These new on-premises server versions will only be available with the purchase of a subscription license, using a similar subscription model to Microsoft 365.
The name for these new on-premises server products has yet to be announced, but it is likely that Microsoft will drop the year from the version name since the new subscription server will be evergreen. Pricing and availability will be announced closer to the release date.
It's important for on-premises customers to know and stay on top of the Exchange Server product lifecycle policies for support and planning.
End of Mainstream Support
End of Extended Support
Exchange Server 2010
Exchange Server 2013
Exchange Server 2016
Exchange Server 2019
As mentioned in the article, Exchange Server 2016 and the End of Mainstream Support, CU19 is the last planned update for Exchange Server 2016 and is due in December 2020. After December 15, 2020, only CU19 or its successors will receive critical updates.
Exchange Server Upgrade Planning
You'll be able to install Exchange Server vNext into an org with Exchange Server 2013, 2016 or 2019. That's one more version than they used to support. And for the first time ever, you'll be able to perform an in-place upgrade from Exchange Server 2019 to Exchange Server vNext. Even in the same DAG. This will make it the easiest Exchange upgrade ever!
The bottom line is, if you're going to be staying on-premises long term - start planning and installing Exchange Server 2019 today!
New hybrid customers or customers who plan to keep some mailboxes on-premises should definitely upgrade to Exchange 2019 and later, Exchange Server vNext when it's released.
Hybrid customers who have completed migrating all their mailboxes to Exchange Online can continue to use their existing Exchange 2016 server for hybrid management. Microsoft hopes to deliver a serverless management solution soon, but it will later than the CU19 release.
Other Exchange and Exchange Online News
Another important bit of news on hybrid is that the new HCW will support establishing a one-to-many on-premises to cloud tenant configuration. This is helpful for divestments and customers with multiple tenants. Just be aware it only works for Exchange 2016/2019 and Hybrid Modern Auth only works with one tenant.
Microsoft is also opening the distribution of the Exchange Server 2019 Capacity Calculator. It previously was available only to Volume License customers. You can get it from https://aka.ms/ExCalc.
"Plus Addressing" is now GA in Exchange Online. This lets users create "disposable" email addresses based on their primary email address. This lets users know where their email addresses are being leaked and create Inbox rules to handle them.
View the on-demand session, Exchange, Here, There and Everywhere, delivered by the ever-so-suave Greg Taylor.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
EXPTA Consulting provides professional upgrade, migration, and hybrid services for on-premises customers of all sizes. We specialize in Exchange, Microsoft 365, Active Directory, and identity solutions and pride ourselves on customer satisfaction.
Examples where we provide turn-key solutions or can work with your IT staff include:
- Exchange and Active Directory Health Checks
- Exchange on-premises upgrades and configuration
- Exchange hybrid configuration and migrations to Exchange Online
- Hybrid Modern Authentication (MFA) for Exchange on-premises
- Public Key Infrastructure (PKI) design and deployment
Microsoft announced that it will be rolling out roaming signatures soon in Outlook for Windows. It's expected that this feature will come to Exchange Online for now. Customers using third-party signature solutions will want to prepare for this. Review Outlook roaming signatures options.
(Updated) Outlook for Windows Introduces Roaming Signatures
MC215017, Plan For Change, Published date: Jun 2, 2020
Major update: Announcement
Applies To: All
This message is associated with Microsoft 365 Roadmap ID 60371
When this will happen
We will begin rolling this out to Microsoft 365 Monthly Channel, Targeted, in late September (previously July). (This is Insiders Slow Channel which will soon be called Microsoft Beta.)
We expect to roll this out to the Monthly Channel, Production, in late October (previously August).
How this will affect your organization
The feature is on by default.
Traditionally, signatures were stored locally on a user's Windows device. With this feature, signatures will now be associated with an email account.
Signatures will be stored in the user mailbox and will be available on any devices running Outlook for Windows that has been configured with that email account.
When the feature becomes available, Outlook will read the existing local signatures. Outlook will copy signatures selected as default for New messages or Replies/forwards to the account mailbox, making them available across multiple devices.
What you need to do to prepare
The feature is on by default.
Because this new feature is changing how Outlook manages signatures stored on a local drive, third-party add-ins which provided this functionality will no longer work when this feature is enabled. Learn how to mitigate this for your users.
I know a lot of customers like me are looking forward to this update!
Microsoft Ignite 2020 is virtually just around the corner (see what I did there?). Get ready for two days of jam-packed content, so set your OOF for September 22-23 so you can join in for all the goodness uninterrupted.
The Exchange Team published a blog article listing all the sessions around Exchange and Outlook. These include Roadmap Sessions, which focus on what's new and upcoming, and Technical Deep Dives and Walk-Throughs, that take you through the specifics of a particular area of interest. There are also many Learning Path sessions describing how to use technologies to deliver successful solutions to your business.
Of particular note, you'll want to see Exchange - Here, There and Everywhere. This is one of the many pre recorded sessions that you can watch on-demand. Look here for exclusive information about about Microsoft's plans for the future of both on-prem and cloud. This is a must-see presentation for planning and forecasting so sign-up here.
When completing your Schedule Scheduler, you'll notice that sessions have two options -- Save to Backpack (for pre-recorded on-demand sessions) or +Add to Schedule (for live digital breakout sessions). If you can't attend the live session you can add it to your backpack to watch later. Live community events will have an RSVP button where you can save a virtual spot.
While no one will argue that an in-person event is preferred, this virtual event promises to deliver some really good content in a way that everyone can consume on their own schedules. "See" you there!
Microsoft 365 retention policies are configured from Policies in the Microsoft 365 Compliance Center (https://compliance.microsoft.com). You can create retention policies to keep and or delete data in Exchange email, SharePoint sites, OneDrive accounts, Office 365 Groups, Skype for Business, Exchange Public Folders, and Teams channel messages and chats.
When setting up a new retention policy it defaults to configure a policy for Exchange email, SharePoint sites, OneDrive accounts, and Office 365 Groups.
As of this writing, separate retention policies are required for Microsoft Teams data.
If you select Exchange Public Folders but you don't have them in Exchange Online, the policy will show an error saying, "1 distribution result(s) found". The Exchange location has the details, "Recipient not found" and the Action will say, "Notify support".
The MVP Award is an important recognition to me and I'm honored to receive it. It includes several benefits, but the most important one to me are all the interactions with the great product groups at Microsoft. These relationships allow me to reach out to specific product team members to provide feedback and get clarification on product features and behaviors.
It's a mutually beneficial partnership -- under NDA, Microsoft is able to talk with MVPs about product futures, provide access to technology adoption programs (TAPs) to test new software, and solicit our MVP feedback. As MVPs, we are able to provide important and honest feedback to the product teams about how new features and behaviors will affect our customers, beta test new software and file bug reports, and be advocates for you, the customer.
As usual, I feel great!
Throttling policies help ensure server reliability and uptime by limiting the amount of server resources that a single user or application can consume in Exchange Online. When high load factors are detected that degrade the performance of these resources, EWS connections are dynamically throttled based on the amount that each caller has contributed to this high load condition.
The result is that the third-party migration tool that uses EWS may be impacted by the EWS throttling policy. Migrations may slow or stop altogether.
See EWS throttling in Exchange for a full description of EWS throttling and limits.
Note: It's important to call out that EWS throttling policies do not affect Exchange hybrid migrations. Hybrid migrations use the RPC over HTTP protocol, not EWS. Do use the steps in this article to try resolving slow hybrid migrations.