Exchange Server Extended Protection
Timelines and exceptionsTimeline
From the capture of 13 Oct 00:08 UTC- 3 dates
- 31 undated sections
- 30 with conditions
- or later; update release August 2022 Published timing is qualified; effectiveness is not confirmed.
- Retired / removed11 Apr 2023 Now: Removed or unsupported
- 5 years agomonth window
- 4 years agomonth windowupdate release · Patch Tuesday 9 Aug 2022
- Exchange 2013in Extended Protection can't be enabled on Exchange Server 2016 CU22 or Exchange Server 2019 CU11 or older that hosts a Public Folder hierarchyMilestone
- Exchange 2016in Extended Protection can't be enabled on Exchange Server 2016 CU22 or Exchange Server 2019 CU11 or older that hosts a Public Folder hierarchyMilestone
- Exchange 2019in Extended Protection can't be enabled on Exchange Server 2016 CU22 or Exchange Server 2019 CU11 or older that hosts a Public Folder hierarchyMilestone
- 3 years agoRetired / removed
Settings and overrides named on this page
Registry values, policies and cmdlets the source mentions, with the dated steps that name them. Read the source for the values to set.
Front-EndMicrosoft-Server-ActiveSyncPublicFolderHierarchyHandlerEnablerOverrideSchUseStrongCryptoOverrideSslNegotiateCertSystemDefaultTlsVersionsOverride
Requirements, exceptions and scope
APPLIES TO: 2016 2019 Subscription Edition…
Windows Extended Protection enhances the existing authentication in Windows Server and mitigates authentication relay or man-in-the-middle (MitM) attacks. This…
SchUseStrongCryptoSystemDefaultTlsVersions- Extended Protection can't be enabled on Exchange Server 2013 servers with Public Folders in a coexistence environmentRequirement1 condition1 passage
- Identifying Exchange servers that are published using Hybrid AgentRequirementExceptionScopeRecommendation2 conditions5 passages
Front-End Microsoft-Server-ActiveSyncSslNegotiateCertFront-End- Enabling Extended Protection by using Exchange Server 2019 CU14 (or later) installerScopeRecommendation1 condition2 passages
- Scenario 1: Enable Extended Protection on all Exchange ServerRequirementException2 conditions3 passages
- Scenario 2: Configure Extended Protection when running a Modern Hybrid configurationRequirement1 condition1 passage
Front-End - Set Extended Protection to required or accept for on a virtual directoryRequirement1 condition6 passages
- Issue: Creating Public Folders by using an Outlook client fails with the following error: 'Cannot create the public folder. You do not have sufficient permissi…Requirement2 conditions2 passages
PublicFolderHierarchyHandlerEnabler - Warnings and errors during Extended Protection configuration script executionRequirementScopeRecommendation4 conditions3 passages
- Users can't access their mailbox through one or more clientsRequirementRecommendationTentative2 conditions2 passages
Front-End
Extracted automatically from Microsoft's wording. Confirm dates, conditions and whether they apply to you in the source before acting; a month or quarter is a window, not a day.
Observed history and review priority
Captured 13 Oct 00:08 UTC; extracted 16 Oct 16:10 UTC. Extractor: microsoft-1/9/fc65ebeb286710c0a830833db8a7e5de7e266b79981fe9c7c34479be9369ad3c.
Review priority. Extracted assertions require review · Publisher marks guidance tentative · Applicability or exceptions require review
0 date changes and 0 condition changes across 0 compared revisions. Suggested check interval: 24 hours.
Earlier unavailable versions and edits between checks are unknown. A missing statement requires review; it does not mean the policy was cancelled. Recovered historical statements are not original revision snapshots.
Retained observations · 2
Compact evidence remains available after full document bodies expire. Earlier extractions can have different vocabulary or capture limitations.
- 13 Oct 00:08 UTC · 126 candidates
- 8 Oct 23:14 UTC · 79 candidates