This means that Exchange online is no longer driving cumulative updates for on-prem. Going forward Microsoft has separated Exchange on-prem into its own code branch. By the time the code was released on-prem, it had been more than validated as stable and able to run at scale. The greatest benefit of this common code was that it ran in the cloud for a number of months before shipping on-prem as a cumulative update. This was a result of Exchange Online and Exchange on-prem sharing a common code base. The tagline for Exchange 2016 was that it was “forged in the cloud”. Here is what Ignite taught us about Exchange 2019. Hopefully, it will also serve as a reference if you need to search for a certain announcement or feature weeks (or even months) down the road. In addition, those notes contain timers so you can jump to the section that interests you the most. Each session in this article includes extensive notes on what each session contained. If not already, I highly recommend checking out 15 Ignite sessions every Exchange admin should see. With 1,610 sessions Microsoft gave us a massive amount of announcements and demonstrations of new product features. It’s amazing to believe that Microsoft Ignite was over a month ago.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |