Updating microsoft outlook 2016 to 2016
We’ll continue to invest in broader availability of endpoints to support search scenarios, particularly connectors, and deliver on the connectors we already ship.In addition we’re shipping some new APIs to support surfacing external sources in Delve (as demonstrated at \build) and have a number of partners in our search TAP program that are actively building connectors using some of our new search experiences and endpoints.And to tie into that will you provide a Single server image that will be needed to test that the baseline functionality will be unaffected.Essentially giving a “pre-Cloud” test bed for companies with Masses of data 10TB To add, the cloud should be viewed as a migration whereas on-premises, an upgrade.Would that create too much overhead on the MS teams to support stuff at the SP/OS level that we may break with farm level customization?We don’t have any plans today for Paa S – for Iaa S and even traditional on-premises scenarios we’re simplifying patch management with 0 downtime and deployment with early investments such as Min Role that will ease the management burden.
Namely subscription apps, common consent, and Office 365 APIs as initial investment areas.
In Share Point Server 2016 updates are orchestrated differently mitigating the offline upgraders as experienced in earlier versions of Share Point, we’re moving to a B2B online upgrade model that alleviates the need for post-patch experiences.
We’ll share more details soon, at a high level patching remains thru MSPs (with significant reduction), but now with 0 downtime, removing dependencies between FE and BE components and now upgraders are all done online.
We’ll support uni-directional sync via AD sync in-product in addition to external MIM for bi-directional sync scenarios.
Effectively we’ve removed the embedded version of FIM and done work to more closely integrate with an external instance.