Home
%3CLINGO-SUB%20id%3D%22lingo-sub-844075%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844075%22%20slang%3D%22en-US%22%3EWhat%20if%20I%20ignore%20the%20UnableToWriteToAadException%3F%20Will%20EXO%20retry%20syncing%20to%20AAD%20at%20a%20later%20moment%20on%20its%20own%20or%20do%20I%20absolutely%20have%20to%20re-run%20the%20cmdlet%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844104%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844104%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F90610%22%20target%3D%22_blank%22%3E%40Victor%3C%2FA%3E-%20you%20will%20need%20to%20retry%20the%20operation%3B%20once%20this%20change%20goes%20into%20the%20effect%2C%20the%20properties%20in%20question%20will%20not%20be%20written%20to%20Exchange%20Online%20if%20the%20write%20to%20AAD%20fails.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844185%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844185%22%20slang%3D%22en-US%22%3E%3CP%3EOof%20-%20I%20feel%20bad%20for%20Dave%20in%20building%2030%20if%20the%20WSYP%20program%20is%20still%20in%20place.%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fblogs.technet.microsoft.com%2Fuktechnet%2F2012%2F04%2F27%2Ffriday-fun-microsoft-wsyp-we-share-your-pain-project%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fblogs.technet.microsoft.com%2Fuktechnet%2F2012%2F04%2F27%2Ffriday-fun-microsoft-wsyp-we-share-your-pain-project%2F%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-844962%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-844962%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20does%20this%20apply%20in%20a%20scenario%20such%20as%20Undo-SoftDeletedMailbox%2C%20where%20the%20cmdlet's%20success%20does%20not%20really%20tell%20the%20whole%20story%20about%20the%20background%20replication%3F%20Would%20those%20operations%20take%20a%20lot%20longer%2C%20or%20would%20they%20have%20the%20same%20failure%20modes%20they%20do%20today%20(e.g.%20potential%20collisions)%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-845966%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-845966%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20in%20total%20this%20sounds%20very%20good%20-%20I%20only%20have%20one%20concern%3A%20what%20is%20the%20performance%20impact%20of%20this%20change%3F%20Updating%20Azure%20AD%20through%20Graph%20API%20is%20very%20slow%20compared%20to%20the%20old%20native%20exchange%20online%20cmdlets.%20Have%20you%20measured%20a%20mass%20update%20for%20let%E2%80%99s%20say%2010.000%20users%20with%20your%20old%20and%20your%20new%20script%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20also%20assume%20changes%20are%20only%20made%20to%20Cmdlets%20with%20the%20set%2Cnew%20or%20update%20verb%3F%20Get%20commands%20still%20grab%20everything%20from%20the%20underlying%20AD%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewould%20be%20nice%20if%20you%20could%20do%20a%20comparison%20and%20share%20your%20results%20%3Bp%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Eregards%3C%2FP%3E%3CP%3Echristian%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-848362%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-848362%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20team%2C%3C%2FP%3E%3CP%3EAny%20plans%20to%20improve%20the%20forward%20sync%20mechanism%20or%20way%20to%20do%20it%20from%20the%20customer%20end%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-849498%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-849498%22%20slang%3D%22en-US%22%3E%3CP%3EHow%20can%20we%20know%20if%20the%20%3CSPAN%20style%3D%22display%3A%20inline%20!important%3B%20float%3A%20none%3B%20background-color%3A%20%23ffffff%3B%20color%3A%20%23333333%3B%20font-family%3A%20'SegoeUI'%2C'Lato'%2C'Helvetica%20Neue'%2CHelvetica%2CArial%2Csans-serif%3B%20font-size%3A%2016px%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20300%3B%20letter-spacing%3A%20normal%3B%20orphans%3A%202%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%22%3Eimprovement%20is%20deployed%20to%20our%20tenant%3C%2FSPAN%3E%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856507%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856507%22%20slang%3D%22en-US%22%3EDoes%20this%20improve%20the%20speed%20of%20AAD%20Connect%3F%20Currently%20we%20sync%20AD%20changes%20hourly%2C%20which%20can%20be%20problematic.%20Then%20Mail%20changes%20from%20O365%20have%20to%20sync%20back%20to%20AD%2C%20which%20can%20be%20very%20problematic.%20Dave%20has%20alot%20to%20answer%20for!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-837218%22%20slang%3D%22en-US%22%3EExchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-837218%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20part%20of%20continued%20improvements%20to%20the%20Exchange%20Online%20service%20we%20are%20releasing%20an%20improvement%20to%20the%20User%20object%20management%20experience.%3C%2FP%3E%3CP%3EToday%2C%20when%20you%20create%20or%20modify%20user%E2%80%99s%20properties%20via%20Exchange%20Admin%20Center%20(EAC)%2C%20Exchange%20Online%20PowerShell%20or%20other%20API%2C%20the%20change%20replicates%20to%20Azure%20Active%20Directory%20(AAD)%20through%20a%20sync%20mechanism%20which%20can%20take%20some%20time%20to%20complete.%20Simply%20put%2C%20you%20might%20not%20see%20the%20result%20of%20your%20change%20in%20AAD%20for%20a%20while.%3C%2FP%3E%3CP%3EThis%20%E2%80%9Cback-sync%E2%80%9D%20mechanism%20(as%20you%20may%20have%20heard%20it%20referred%20to)%20from%20Exchange%20Online%20to%20AAD%20has%20served%20us%20well%20for%20many%20years%20making%20sure%20the%20data%20in%20both%20directories%20(which%20sometimes%20includes%20an%20on-premises%20directory%20if%20you%20have%20AAD%20Connect%20or%20Exchange%20Hybrid%20enabled)%20remains%20in%20sync.%20This%20sync%20mechanism%20provides%20key%20functionality%20that%20AAD%20and%20Exchange%20Online%20depend%20upon.%3C%2FP%3E%3CP%3EHowever%2C%20this%20back-sync%20mechanism%20can%20sometimes%20become%20slow%20(due%20to%20various%20reasons%20that%20we%20won%E2%80%99t%20go%20into%20here%20(we%20suspect%20it's%20someone%20called%20Dave%20in%20building%2030)).%20If%20that%20happens%2C%20changes%20might%20not%20appear%20in%20AAD%20in%20a%20timely%20manner.%20This%20prevents%20admins%20from%20seeing%20a%20properly%20updated%20graph%20view%20in%20AAD%20or%20making%20additional%20changes%20like%20licensing%20or%20UPN%20changes%20(these%20changes%20mastered%20in%20AAD%20vs.%20mastered%20in%20EXO).%3C%2FP%3E%3CP%3EThe%20Exchange%20Online%20and%20AAD%20teams%20have%20worked%20together%20to%20provide%20a%20new%20mechanism%20to%20synchronize%20the%20changes%20that%20originate%20in%20EXO%20and%20need%20to%20replicate%20to%20AAD%20without%20relying%20on%20the%20current%20back-sync%20mechanism.%3C%2FP%3E%3CP%3EOnce%20this%20improvement%20is%20deployed%20to%20your%20tenant%2C%20when%20you%20make%20user%20object%20changes%20in%20Exchange%20the%20changes%20will%20now%20be%20dual-written%20to%20AAD%20and%20EXO.%20The%20end%20result%20is%20that%20the%20replication%20of%20those%20properties%20should%20be%20close%20to%20immediate%20and%20changes%20made%20in%20EXO%20will%20immediately%20reflect%20in%20AAD%20when%20the%20cmdlet%20completes%20successfully.%3C%2FP%3E%3CP%3ENote%20that%20this%20implies%20that%20there%20is%20now%20an%20AAD%20dependency%20when%20making%20such%20management%20changes.%20If%20AAD%20is%20unavailable%20for%20some%20reason%20when%20we%20attempt%20this%20dual-write%20you%20may%20see%20errors%20when%20executing%20an%20Exchange%20cmdlet%20or%20management%20action.%20This%20error%20will%20reference%20AAD.%20Note%2C%20that%20this%20change%20should%20be%20transparent%20to%20all%20the%20Exchange%20management%20operations%20you%20are%20doing%20today.%20There%20is%20absolutely%20no%20need%20to%20change%20your%20scripts%20or%20your%20usage%20of%20EAC%20or%20other%20Exchange%20APIs.%20You%20maysee%20new%20errors%2C%20but%20they%20should%20be%20treated%20the%20same%20as%20you%20do%20today%3A%20re-run%20the%20cmdlet.%20If%20the%20issue%20persists%20when%20you%20open%20a%20support%20ticket%2C%20just%20mention%20that%20the%20error%20in%20Exchange%20is%20due%20to%20AAD%20and%20support%20should%20be%20able%20to%20help%20you%20redirect%20to%20the%20correct%20teams.%3C%2FP%3E%3CP%3EHere%20is%20an%20example%20of%20the%20cmdlet%20error%20that%20you%20might%20see.%20You%20can%20always%20get%20more%20detailed%20information%20if%20you%20get%20the%20full%20error%20trace%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%5BMultiTenant%5CBL0PR00MB0354%5D%20PS%20C%3A%5CUsers%5Cchsun%26gt%3B%20set-mailbox%20testDareen%40dualwritetesting.onmicrosoft.com%20-CustomAttribute1%20%22demo%20test%22%20An%20Azure%20Active%20Directory%20call%20was%20made%20to%20keep%20object%20in%20sync%20between%20Azure%20Active%20Directory%20and%20Exchange%20Online.%20However%2C%20it%20failed.%20The%20issue%20may%20be%20transient%20and%20please%20retry%20a%20couple%20of%20minutes%20later.%20If%20issue%20persists%2C%20please%20see%20exception%20members%20for%20more%20information.%20%2B%20CategoryInfo%20%3A%20NotSpecified%3A%20(%3A)%20%5BSet-Mailbox%5D%2C%20UnableToWriteToAadException%20%2B%20FullyQualifiedErrorId%20%3A%20%5BServer%3DBL0PR00MB0354%2CRequestId%3D6669e8ca-2919-450f-93d7-5757b75bef45%2CTimeStamp%3D3%2F15%2F2019%209%3A07%3A01%20PM%5D%20%5BFailureCategory%3DCmdlet-UnableToWriteToAadException%5D%20B6FABBF%2CMicrosoft.Exchange.Management.RecipientT%20asks.SetMailbox%20%2B%20PSComputerName%20%3A%20bl0pr00mb0354.namprd00.prod.outlook.com%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20hope%20you%20agree%20that%20this%20change%20is%20a%20good%20thing.%20We%20really%20want%20your%20admin%20and%20management%20experience%20to%20be%20as%20efficient%20and%20useful%20as%20possible%2C%20and%20this%20change%20eliminates%20one%20issue%20we%20were%20aware%20of%20that%20caused%20some%20pain.%3C%2FP%3E%3CP%3EPlease%20do%20let%20us%20know%20what%20you%20think%20in%20the%20comments%20section%20below%2C%20and%20we%20hope%20you%20notice%20the%20improvement!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20Exchange%20Team%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-837218%22%20slang%3D%22en-US%22%3E%3CP%3EAs%20part%20of%20continued%20improvements%20to%20the%20Exchange%20Online%20service%2C%20we%20are%20releasing%20an%20improvement%20to%20the%20User%20object%20management%20experience.%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-837218%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdministration%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EAnnouncements%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EExchange%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EScripting%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-862658%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-862658%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F336137%22%20target%3D%22_blank%22%3E%40jamsnz%3C%2FA%3E%26nbsp%3BYou%20can%20change%20the%20scheduler%20to%20even%205%20minutes%20if%20you%20need%20to.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ESet-ADSyncScheduler%20-CustomizedSyncCycleInterval%20d.HH%3Amm%3Ass%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867415%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867415%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387901%22%20target%3D%22_blank%22%3E%40Opti-IT%3C%2FA%3E%20You%20cannot%20change%20the%20Sync%20cycle%20interval%20less%20than%2030%20minutes.%20When%20you%20run%20Get-ADSyncScheduler%2C%20the%20AllowedSyncCycleInterval%20is%20set%20to%2030%20minutes.%20Any%20values%20set%20to%20a%20cycle%20lower%20than%2030%20minutes%20will%20default%20to%2030.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867420%22%20slang%3D%22en-US%22%3ERe%3A%20Exchange%20Online%20Improvements%20to%20Accelerate%20Replication%20of%20Changes%20to%20Azure%20Active%20Directory%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867420%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3207%22%20target%3D%22_blank%22%3E%40Josh%20Villagomez%3C%2FA%3E%26nbsp%3BOh%2C%20thanks%20for%20that%2C%20you%20are%20right%2C%20of%20course.%3C%2FP%3E%3C%2FLINGO-BODY%3E

As part of continued improvements to the Exchange Online service we are releasing an improvement to the User object management experience.

Today, when you create or modify user’s properties via Exchange Admin Center (EAC), Exchange Online PowerShell or other API, the change replicates to Azure Active Directory (AAD) through a sync mechanism which can take some time to complete. Simply put, you might not see the result of your change in AAD for a while.

This “back-sync” mechanism (as you may have heard it referred to) from Exchange Online to AAD has served us well for many years making sure the data in both directories (which sometimes includes an on-premises directory if you have AAD Connect or Exchange Hybrid enabled) remains in sync. This sync mechanism provides key functionality that AAD and Exchange Online depend upon.

However, this back-sync mechanism can sometimes become slow (due to various reasons that we won’t go into here (we suspect it's someone called Dave in building 30)). If that happens, changes might not appear in AAD in a timely manner. This prevents admins from seeing a properly updated graph view in AAD or making additional changes like licensing or UPN changes (these changes mastered in AAD vs. mastered in EXO).

The Exchange Online and AAD teams have worked together to provide a new mechanism to synchronize the changes that originate in EXO and need to replicate to AAD without relying on the current back-sync mechanism.

Once this improvement is deployed to your tenant, when you make user object changes in Exchange the changes will now be dual-written to AAD and EXO. The end result is that the replication of those properties should be close to immediate and changes made in EXO will immediately reflect in AAD when the cmdlet completes successfully.

Note that this implies that there is now an AAD dependency when making such management changes. If AAD is unavailable for some reason when we attempt this dual-write you may see errors when executing an Exchange cmdlet or management action. This error will reference AAD. Note, that this change should be transparent to all the Exchange management operations you are doing today. There is absolutely no need to change your scripts or your usage of EAC or other Exchange APIs. You may see new errors, but they should be treated the same as you do today: re-run the cmdlet. If the issue persists when you open a support ticket, just mention that the error in Exchange is due to AAD and support should be able to help you redirect to the correct teams.

Here is an example of the cmdlet error that you might see. You can always get more detailed information if you get the full error trace:

 

[MultiTenant\BL0PR00MB0354] PS C:\Users\chsun> set-mailbox testDareen@dualwritetesting.onmicrosoft.com -CustomAttribute1 "demo test"
An Azure Active Directory call was made to keep object in sync between Azure Active Directory and Exchange Online. However, it failed. The issue may be transient and please retry a couple of minutes later. If issue persists, please see exception members for more information.

    + CategoryInfo          : NotSpecified: (:) [Set-Mailbox], UnableToWriteToAadException
    + FullyQualifiedErrorId : [Server=BL0PR00MB0354,RequestId=6669e8ca-2919-450f-93d7-5757b75bef45,TimeStamp=3/15/2019
    9:07:01 PM] [FailureCategory=Cmdlet-UnableToWriteToAadException] B6FABBF,Microsoft.Exchange.Management.RecipientT
  asks.SetMailbox
    + PSComputerName        : bl0pr00mb0354.namprd00.prod.outlook.com

 

We hope you agree that this change is a good thing. We really want your admin and management experience to be as efficient and useful as possible, and this change eliminates one issue we were aware of that caused some pain.

Please do let us know what you think in the comments section below, and we hope you notice the improvement!

 

The Exchange Team

11 Comments
Occasional Visitor
What if I ignore the UnableToWriteToAadException? Will EXO retry syncing to AAD at a later moment on its own or do I absolutely have to re-run the cmdlet?
Microsoft
@Victor - you will need to retry the operation; once this change goes into the effect, the properties in question will not be written to Exchange Online if the write to AAD fails.
Frequent Contributor

Oof - I feel bad for Dave in building 30 if the WSYP program is still in place. https://blogs.technet.microsoft.com/uktechnet/2012/04/27/friday-fun-microsoft-wsyp-we-share-your-pai...

Occasional Contributor

How does this apply in a scenario such as Undo-SoftDeletedMailbox, where the cmdlet's success does not really tell the whole story about the background replication? Would those operations take a lot longer, or would they have the same failure modes they do today (e.g. potential collisions)?

Regular Visitor

Hi, in total this sounds very good - I only have one concern: what is the performance impact of this change? Updating Azure AD through Graph API is very slow compared to the old native exchange online cmdlets. Have you measured a mass update for let’s say 10.000 users with your old and your new script?

 

I also assume changes are only made to Cmdlets with the set,new or update verb? Get commands still grab everything from the underlying AD?

 

would be nice if you could do a comparison and share your results ;p

 

regards

christian 

New Contributor

Hi team,

Any plans to improve the forward sync mechanism or way to do it from the customer end?

How can we know if the improvement is deployed to our tenant?

Occasional Visitor
Does this improve the speed of AAD Connect? Currently we sync AD changes hourly, which can be problematic. Then Mail changes from O365 have to sync back to AD, which can be very problematic. Dave has alot to answer for!
Occasional Contributor

@jamsnz You can change the scheduler to even 5 minutes if you need to.

 

Set-ADSyncScheduler -CustomizedSyncCycleInterval d.HH:mm:ss

 

Microsoft

@Opti-IT You cannot change the Sync cycle interval less than 30 minutes. When you run Get-ADSyncScheduler, the AllowedSyncCycleInterval is set to 30 minutes. Any values set to a cycle lower than 30 minutes will default to 30. 

Occasional Contributor

@Josh Villagomez Oh, thanks for that, you are right, of course.