%3CLINGO-SUB%20id%3D%22lingo-sub-1455299%22%20slang%3D%22en-US%22%3EChanges%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1455299%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20we're%20posting%20about%20an%20upcoming%20change%20that%20might%20impact%20customers%20who%20use%20the%20Intune%20Exchange%20On-Premises%20Connector.%20%3CBR%20%2F%3E%3CSTRONG%3EIntune%20Deprecating%20the%20Exchange%20On-Premises%20Connector%3C%2FSTRONG%3E%3CBR%20%2F%3EIntune%20is%20deprecating%20the%20Exchange%20On-Premises%20Connector%20feature%20from%20the%20Intune%20service.%20This%20does%20%3CEM%3Enot%3C%2FEM%3E%20affect%20existing%20customers%20with%20an%20active%20connector%2C%20they%20will%20be%20able%20to%20continue%20using%20the%20connector%20for%20the%20time%20being.%3C%2FP%3E%0A%3CP%3EThe%20only%20customers%20that%20will%20be%20impacted%20are%20those%20%3CEM%3Ethat%20do%20not%20have%20an%20existing%20active%20connector.%3C%2FEM%3E%20Those%20customers%20will%20no%20longer%20be%20able%20to%20create%20new%20connectors%20or%20manage%20on-premises%20EAS%20devices%20from%20Intune.%3CBR%20%2F%3E%3CSTRONG%3EHow%20this%20will%20affect%20your%20organization%3C%2FSTRONG%3E%3CBR%20%2F%3EIf%20you%20are%20not%20already%20using%20the%20Exchange%20On-Premises%20Connector%2C%20but%20want%20the%20functionality%20this%20service%20provides%2C%20you%20will%20need%20to%20use%20a%20different%20method%20to%20enable%20Conditional%20Access%20for%20Exchange%20on-premises.%20Microsoft%20recommends%20the%20use%20of%20Exchange%20hybrid%20modern%20authentication%20(HMA)%20to%20protect%20access%20to%20Exchange%20on-premises.%20HMA%20enables%20both%20Intune%20App%20Protection%20Policies%20(also%20known%20as%20MAM)%20and%20Conditional%20Access%20through%20Outlook%20mobile%20for%20Exchange%20on-premises.%3CBR%20%2F%3E%3CSTRONG%3EWhat%20you%20need%20to%20do%20to%20prepare%3C%2FSTRONG%3E%3CBR%20%2F%3EIf%20you%20are%20an%20existing%20tenant%20with%20an%20active%20connector%2C%20you%20will%20be%20able%20to%20continue%20with%20the%20current%20functionality%20at%20this%20time.%20For%20all%20other%20customers%2C%20consider%20your%20Exchange%20environment%20requirements%20and%20review%20the%20Exchange%20HMA%20if%20you%20need%20protected%20access%20to%20Exchange%20on-premises.%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20any%20questions%20on%20this%20upcoming%20change%2C%20just%20comment%20back%20or%20ask%20your%20question%20directly%20by%20tagging%20%40intunesuppteam%20on%20Twitter!%3C%2FP%3E%0A%3CP%3E%3CFONT%20color%3D%22%23FF6600%22%3EThe%20Exchange%20and%20Intune%20Teams%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1455299%22%20slang%3D%22en-US%22%3E%3CP%3EToday%2C%20we're%20posting%20about%20an%20upcoming%20change%20that%20might%20impact%20customers%20who%20use%20the%20Intune%20Exchange%20On-Premises%20Connector.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1455299%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Eall%20posts%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EClient%20Access%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EHybrid%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Emobility%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOn%20Premises%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1457949%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1457949%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20we%20enable%20HMA%20how%20does%20it%20impact%20the%20end%20users%20using%20outlook2010%2C%202013%2C2016(Prerequisites%20says%20from%20outlook%202013%20it%20supports)%20.we%20are%20using%20legacy%20protcols%20like%20imap%2C%20pop3%20whether%20it%20will%20be%20impacted.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1459924%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1459924%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F354073%22%20target%3D%22_blank%22%3E%40Kiran2150%3C%2FA%3E%20enabling%20HMA%20doesn't%20disable%20legacy%20auth.%20It's%20additional.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1467016%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1467016%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20basically%20that%20means%20users%20could%20use%20native%20app%20as%20well%20as%20outlook%20mobile%20app%2C%20the%20latter%20having%20the%20advantage%20of%20IAP%20%2B%20CA%20over%20the%20former%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1468186%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1468186%22%20slang%3D%22en-US%22%3E%3CP%3EHMA%20in%20Outlook%20iOS%20requires%20data%20to%20be%20'synced'%20to%20Exchange%20Online%20-%20any%20way%20to%20avoid%20this%20and%20ensure%20data%20is%20still%20on-prem%2C%20or%20do%20we%20need%20to%20use%20the%20natve%20mail%20client%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1469204%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1469204%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F379843%22%20target%3D%22_blank%22%3E%40RahulSingh%3C%2FA%3E%2C%20correct.%20Have%20a%20look%20at%20our%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2FExchange%2Fclients%2Foutlook-for-ios-and-android%2Fuse-hybrid-modern-auth%3Fview%3Dexchserver-2019%23implementation-steps%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EIntune%20App%20Protection%20and%20Conditional%20Access%20with%20HMA%3C%2FA%3E%26nbsp%3Bdoc%20to%20learn%20more%20about%20these%20features.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1469305%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1469305%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F688053%22%20target%3D%22_blank%22%3E%40apnet1205%3C%2FA%3E%26nbsp%3B-%26nbsp%3BOutlook%20for%20iOS%20and%20Android%20(Outlook%20mobile)%20has%20always%20been%20a%20cloud-backed%20application.%20Processing%20information%20in%20our%20service%20fabric%20enables%20advanced%20features%20and%20capabilities%2C%20such%20as%20the%20categorization%20of%20email%20for%20the%20Focused%20Inbox%2C%20improved%20search%20speed%2C%20artificial%20intelligence%20scenarios%2C%20and%20more.%20It%20enhances%20Outlook%E2%80%99s%20performance%20and%20stability%2C%20relying%20on%20the%20Outlook%20service%20for%20intensive%20processing%20and%20minimizing%20the%20resources%20required%20from%20users'%20devices.%20Lastly%2C%20it%20allows%20Outlook%20to%20build%20features%20that%20work%20across%20all%20email%20accounts%2C%20regardless%20of%20the%20technological%20capabilities%20of%20the%20underlying%20messaging%20platforms%20(e.g.%20different%20versions%20of%20Exchange%2C%203rd%20party%20email%20systems%20like%20Yahoo!%20Mail%20and%20Gmail%2C%20etc.).%20There%20are%20no%20plans%20to%20provide%20an%20Outlook%20mobile%20experience%20that%20does%20not%20rely%20on%20cloud%20integration.%3CBR%20%2F%3E%3CBR%20%2F%3EBut%20let's%20break%20this%20down.%20What%20do%20you%20have%20today%3F%20You%20have%20a%20on-premises%20Exchange%20server%20and%20a%20mobile%20EAS%20device%20(and%20possibly%20laptops%20with%20Outlook%20cached%20mode).%20The%20mobile%20EAS%20device%20contains%20a%20portion%20of%20the%20user's%20mailbox%20data.%20This%20mobile%20EAS%20device%20(and%20laptop!)%20roams%20wherever%20the%20user%20goes%20-%20in-country%2C%20out-country%2C%20etc.%20All%20changes%20that%20the%20user%20enacts%20on%20the%20mobile%20device%20are%20synced%20to%20the%20on-premises%20Exchange%20server%20which%20is%20considered%20the%20authoritative%20source.%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3ENow%20let's%20look%20at%20the%20Outlook%20mobile%20architecture%20(%3CA%20href%3D%22http%3A%2F%2Faka.ms%2Fhmaom%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2Faka.ms%2Fhmaom%3C%2FA%3E).%20You%20have%20a%20mobile%20app%2C%20EXO%2C%20and%20on-premises%20Exchange.%20What%20is%20EXO%20in%20this%20scenario%3F%20It's%20nothing%20more%20than%20the%20mobile%20EAS%20device%20in%20the%20previous%20example%20-%20it%20syncs%20a%20portion%20of%20the%20mailbox%20data%20from%20on-premises%20using%20EAS.%20The%20authoritative%20source%20is%20still%20on-premises%20Exchange%20(e.g%2C%20message%20transport%20occurs%20via%20on-premises).%20Outlook%2BEXO%20%3D%20%22mobile%20EAS%20device%22.%20And%20you%20get%20all%20the%20benefits%20from%20a%20security%2C%20privacy%2C%20and%20compliance%20perspective%20that%20O365%20provides.%20Plus%2C%20you%20get%20additional%20capabilities%20like%20Conditional%20Access%20and%20Intune%20App%20Protection%20Policies%20that%20you%20may%20not%20have%20available%20with%20traditional%20EAS%20clients%2C%20which%20further%20protects%20the%20data%20on%20the%20physical%20device%20and%20ensures%20only%20trusted%20users%20gain%20access%20to%20the%20data.%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20the%20event%20you%20have%20a%20legal%20requirement%20that%20a%20portion%20of%20the%20mailbox%20data%20cannot%20reside%20in%20a%20cloud%20service%20(but%20again%20challenge%20the%20notion%20if%20the%20authoritative%20and%20complete%20source%20remains%20on-premises%20and%20traditional%20EAS%20mobile%20devices%20are%20allowed%20out%20of%20country!)%2C%20then%20yes%2C%20the%20native%20mail%20clients%20are%20your%20only%20option%20(remember%2C%20there%20are%20other%20third-party%20client%20apps%20out%20there%20that%20sync%20data%20to%20cloud%20repositories).%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1471741%22%20slang%3D%22en-US%22%3ERe%3A%20Changes%20to%20the%20Intune%20Exchange%20On-Premises%20Connector%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1471741%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20feels%20premature.%26nbsp%3B%20It%20should%20coincide%20directly%20with%20Exchange%202010%20EOL%20and%20nothing%20else%20sooner.%3C%2FP%3E%3C%2FLINGO-BODY%3E

Today, we're posting about an upcoming change that might impact customers who use the Intune Exchange On-Premises Connector.
Intune Deprecating the Exchange On-Premises Connector
Intune is deprecating the Exchange On-Premises Connector feature from the Intune service. This does not affect existing customers with an active connector, they will be able to continue using the connector for the time being.

The only customers that will be impacted are those that do not have an existing active connector. Those customers will no longer be able to create new connectors or manage on-premises EAS devices from Intune.
How this will affect your organization
If you are not already using the Exchange On-Premises Connector, but want the functionality this service provides, you will need to use a different method to enable Conditional Access for Exchange on-premises. Microsoft recommends the use of Exchange hybrid modern authentication (HMA) to protect access to Exchange on-premises. HMA enables both Intune App Protection Policies (also known as MAM) and Conditional Access through Outlook mobile for Exchange on-premises.
What you need to do to prepare
If you are an existing tenant with an active connector, you will be able to continue with the current functionality at this time. For all other customers, consider your Exchange environment requirements and review the Exchange HMA if you need protected access to Exchange on-premises.

If you have any questions on this upcoming change, just comment back or ask your question directly by tagging @intunesuppteam on Twitter!

The Exchange and Intune Teams

7 Comments
Senior Member

If we enable HMA how does it impact the end users using outlook2010, 2013,2016(Prerequisites says from outlook 2013 it supports) .we are using legacy protcols like imap, pop3 whether it will be impacted. 

@Kiran2150 enabling HMA doesn't disable legacy auth. It's additional.

Senior Member

So basically that means users could use native app as well as outlook mobile app, the latter having the advantage of IAP + CA over the former?

Occasional Visitor

HMA in Outlook iOS requires data to be 'synced' to Exchange Online - any way to avoid this and ensure data is still on-prem, or do we need to use the natve mail client?

@RahulSingh, correct. Have a look at our Intune App Protection and Conditional Access with HMA doc to learn more about these features.

Microsoft

@apnet1205 - Outlook for iOS and Android (Outlook mobile) has always been a cloud-backed application. Processing information in our service fabric enables advanced features and capabilities, such as the categorization of email for the Focused Inbox, improved search speed, artificial intelligence scenarios, and more. It enhances Outlook’s performance and stability, relying on the Outlook service for intensive processing and minimizing the resources required from users' devices. Lastly, it allows Outlook to build features that work across all email accounts, regardless of the technological capabilities of the underlying messaging platforms (e.g. different versions of Exchange, 3rd party email systems like Yahoo! Mail and Gmail, etc.). There are no plans to provide an Outlook mobile experience that does not rely on cloud integration.

But let's break this down. What do you have today? You have a on-premises Exchange server and a mobile EAS device (and possibly laptops with Outlook cached mode). The mobile EAS device contains a portion of the user's mailbox data. This mobile EAS device (and laptop!) roams wherever the user goes - in-country, out-country, etc. All changes that the user enacts on the mobile device are synced to the on-premises Exchange server which is considered the authoritative source. 

Now let's look at the Outlook mobile architecture (http://aka.ms/hmaom). You have a mobile app, EXO, and on-premises Exchange. What is EXO in this scenario? It's nothing more than the mobile EAS device in the previous example - it syncs a portion of the mailbox data from on-premises using EAS. The authoritative source is still on-premises Exchange (e.g, message transport occurs via on-premises). Outlook+EXO = "mobile EAS device". And you get all the benefits from a security, privacy, and compliance perspective that O365 provides. Plus, you get additional capabilities like Conditional Access and Intune App Protection Policies that you may not have available with traditional EAS clients, which further protects the data on the physical device and ensures only trusted users gain access to the data.

In the event you have a legal requirement that a portion of the mailbox data cannot reside in a cloud service (but again challenge the notion if the authoritative and complete source remains on-premises and traditional EAS mobile devices are allowed out of country!), then yes, the native mail clients are your only option (remember, there are other third-party client apps out there that sync data to cloud repositories).

Contributor

This feels premature.  It should coincide directly with Exchange 2010 EOL and nothing else sooner.