Force Immediate Azure AD Connect Sync of New User

AZ-104 By islever Editorial Last updated

Manage Microsoft Entra users and groups

Short answer

B Start-ADSyncSyncCycle -PolicyType Initial runs a full sync cycle; use -PolicyType Delta to replicate the new on-premises user to Azure AD immediately.

Question

Note: The question is included in a number of questions that depicts the identical set-up. However, every question has a distinctive result. Establish if
the solution satisfies the requirements.
Your company has an Azure Active Directory (Azure AD) tenant named weyland.com that is configured for hybrid coexistence with the on-premises Active
Directory domain.
You have a server named DirSync1 that is configured as a DirSync server.
You create a new user account in the on-premise Active Directory. You now need to replicate the user information to Azure AD immediately.
Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet.
Does the solution meet the goal?
  1. Yes
  2. No Correct Answer

Key Takeaways

The test measures whether you know that -PolicyType Initial launches a full import/full sync/export cycle across all connectors, so it cannot satisfy an 'immediately' requirement where -PolicyType Delta is the documented urgent-change switch.

This AZ-104 scenario asks whether running Start-ADSyncSyncCycle -PolicyType Initial will immediately replicate a newly created on-premises Active Directory user to the weyland.com Azure AD tenant. The page establishes that the answer is No, because only -PolicyType Delta delivers the urgent, targeted sync cycle the requirement calls for.

Common mistake: Choosing A (Yes), because an Initial cycle would eventually create the user in Azure AD; learners overlook that a full sync cycle is lengthy and that Microsoft prescribes -PolicyType Delta for urgent manual synchronization.

Expert Analysis

Why the Answer Is Correct

Option B (No) is correct because the requirement is explicit: the new on-premises user must reach Azure AD immediately. Microsoft's Azure AD Connect feature scheduler documentation states that a full sync cycle consists of Full Import on all Connectors, Full Sync on all Connectors, and Export on all Connectors, which is a heavy, time-consuming operation. The same documentation prescribes the Delta policy for urgent changes, so running Start-ADSyncSyncCycle -PolicyType Initial on DirSync1 does not satisfy the timing requirement. As GoldenDisciple2 quoted from the official article, "then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta" is the sanctioned way to push a change right away. Therefore the proposed solution fails the stated goal and the answer is No.

Why the Other Options Are Wrong

Option A (Yes) would only be defensible if the question asked merely whether the user is eventually created, but the operative word is 'immediately' — an Initial cycle performs full discovery and processing of every connected source, which can take many minutes or longer on a real hybrid tenant. skydivex argued that A is right because the scenario never says an initial sync has already run, but that objection misses the point: even in a never-synced environment, the Delta policy is what the product documents for a manually triggered urgent cycle, and the Initial policy is reserved for provisioning or disaster-recovery style full rebuilds. Treating the Initial cmdlet as an 'immediate' mechanism conflates completeness with speed, which is exactly the distinction this question is built to test.

Community Comment Notes

imartinez captured the core reasoning, noting that "Delta, will kick off a delta sync and bring only the last change" and therefore fulfills the immediate requirement, and Bere added that using -PolicyType Initial "will perform a full sync and add the user account created but it will take time." GoldenDisciple2 backed this with the official scheduler article, and Mikeyo likewise cited the same doc while listing the Full Import/Full Sync/Export steps. On the opposing side, skydivex voted A arguing the initial sync may never have completed, while jensdevopstraining treated this as one variant of a three-part question and favored A; juniorccs openly asked "where am I lost here?" about the Delta-versus-Initial distinction, which is precisely the trap the correct answer resolves.

Official Reference

These links open the official vendor documentation in a new tab.

Exam Strategy

On hybrid sync questions, flag any timing adverbs — 'immediately', 'right away', 'urgently' — because they map directly to -PolicyType Delta, while Initial signals a full rebuild. Never assume an unstated prerequisite (like a missing initial sync) to justify an option; judge the cmdlet against the literal requirement.

Frequently Asked Questions

Why doesn't Start-ADSyncSyncCycle -PolicyType Initial sync a new user immediately?

Initial triggers a full sync cycle — Full Import, Full Sync, and Export on all connectors — which is far slower than the targeted Delta cycle needed for one urgent change.

Which cmdlet replicates one new on-premises user to Azure AD right away?

Run Start-ADSyncSyncCycle -PolicyType Delta from an elevated PowerShell prompt on the DirSync1 Azure AD Connect server to push only the latest directory changes.

More AZ-104 FAQ →

Discussion 229 contributions

Compiled from public community threads and reader submissions, lightly edited for clarity. Handles and vote tallies are shown as recorded, and comments reflect the views of individual contributors.

From public community threads 30 of 229

  1. imartinez 👍 137
    Answer is B ( No ) Initial will perform a full sync and add the user account created but it will take time, Delta, will kick off a delta sync and bring only the last change, so it will be "immediately" and will fulfill the requirements.
  2. Bere 👍 33
    In the solution of this question they say “-PolicyType Initial”. However you must use “-PolicyType Delta” to get only the change made and sync it immediately. So the answer is “No”.
  3. GoldenDisciple2 👍 25 Answered B
    https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler In this article. It says word for word, "It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta." Keywords in this learn.microsoft article are immediately and manually.... If you want it to synchronize immediately, then you'll want to manually run a cycle.... To run a cycle manually, run the -delta command. Immediate = Manual. Manual = Delta. Therefor Immediate = Delta Full sync = Time Consuming. Time Consuming = Initial
  4. skydivex 👍 13
    The answer is A (YES), since the question did not mention the initial sync has been already done. A is correct
  5. arunet 👍 9
    B is the answer. https://techcommunity.microsoft.com/t5/itops-talk-blog/powershell-basics-how-to-force-azuread-connect-to-sync/ba-p/887043
Show 25 more comments
  1. jensdevopstraining 👍 8 Answered A
    This question has 3 variants: 1. Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet. 2. Solution: You use Active Directory Sites and Services to force replication of the Global Catalog on a domain controller. 3. Solution: You restart the NetLogon service on a domain controller. We all agree solution 2 and 3 are wrong. I think everyone that thinks the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet solution is wrong is focusing too much on the word "immediately". It will start the sync immediately. It will just take some time. The question does not ask for the quickest solution, it is asking for to start the sync immediately. I think Microsoft has at least 1 correct answer to this question set and therefore I will answer A on this.
  2. BenStokes 👍 7
    Wrong answer. It is B. Delta sync should be used since initial will do full sync. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Ref # https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
  3. Mikeyo 👍 6
    For Immediate sync use -> Start-ADSyncSyncCycle -PolicyType Delta. https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler Full sync cycle A full sync cycle includes the following steps: Full Import on all Connectors Full Sync on all Connectors Export on all Connectors It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Running a full sync cycle can be very time consuming, read the next section to read how to optimize this process.
  4. juniorccs 👍 6
    if the delta will be bring the last changes, so it's okay here, isn't it ? the answer should be then "YES" , correct ? where am I lost here ?
  5. GenjamBhai 👍 6
    B is ok, delta for immediate sync, initial will take longer
  6. Ahja666 👍 5 Answered B
    B is correct. "It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Running a full sync cycle can be very time consuming, read the next section to read how to optimize this process." https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
  7. Pancit 👍 4 Answered A
    The question is tricky and it doesn't indicate how large the On-prem AD is... You all assume it is a large infrastructure what if it is just a 10 to a 100 users.. It doesn't also indicate if the full sync cycle has occurred already for all we know the admin just created the sync server 15 min ago and untick the start sync process after installation of Azure AD connect which means full sync cycle haven't occurred yet.. Start-ADSyncSyncCycle -PolicyType Initial = This will get the job done regardless how big or small the infrastructure is. Even if the sync server was just created 15min ago, this will work regardless if the full sync cycle occurred already. The question will this achieve its goal to replicate AD? = YES
  8. kklohit 👍 4 Answered B
    The solution partially meets the goal. The Start-ADSyncSyncCycle -PolicyType Initial cmdlet initiates an initial sync cycle, which replicates all the changes from on-premises Active Directory to Azure AD. However, it is not recommended to use this cmdlet unless it is the first synchronization cycle because it will affect the performance of the server. Instead, you should use the Start-ADSyncSyncCycle -PolicyType Delta PowerShell cmdlet, which will replicate only the changes made to the on-premises Active Directory since the last synchronization cycle. This cmdlet will allow you to replicate the new user account to Azure AD immediately
  9. VGRY 👍 4
    For the scenario where a new user account has been created in the on-premises Active Directory and needs to be replicated to Azure AD immediately, using the -PolicyType Initial parameter with the Start-ADSyncSyncCycle cmdlet would be the better option. This is because the Initial policy type triggers a full synchronization of all objects in the on-premises Active Directory to Azure AD, while the Delta policy type only synchronizes changes that have occurred since the last synchronization. Since the new user account is not yet synchronized to Azure AD, a full synchronization is required to ensure that it is replicated immediately.
  10. theOldOne 👍 4
    When I read the question as "immediately" I think of it as not waiting for the automatic sync that would occur at a set interval and possibly delay someone logging in. By running the command I am forcing an "immediate" sync of the info. Sometimes it is difficult to tell what they are looking for as sometimes they want you to be as literal as possible and other times they expect you to understand what they are asking. In this case it does meet the objective that we do not have to wait for the auto sync but running the delta option may have been faster. So strange a question.
  11. Bere 👍 4
    As described here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Running a full sync cycle can be very time consuming, so if you need to replicate the user information to Azure AD immediately then run Start-ADSyncSyncCycle -PolicyType Delta. Answer is B. No
  12. DF22 👍 4
    Don't rely on 3rd party blogs. Use the MS documentation. The answer is B. It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler
  13. DataTraveler 👍 4 Answered B
    The answer is explicitly stated in the Microsoft documentation at https://learn.microsoft.com/en-us/entra/identity/hybrid/connect/how-to-connect-sync-feature-scheduler "It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta."
  14. awsazgc 👍 4
    Other options for this question: Solution: You run the Start-ADSyncSyncCycle -PolicyType Initial PowerShell cmdlet. NO Solution: You use Active Directory Sites and Services to force replication of the Global Catalog on a domain controller. NO Solution: You restart the NetLogon service on a domain controller. NO Okay, then what is the answer?
  15. GabeCanada 👍 4
    "Initial" will force a full Sync while "Delta" just the changes since last sync. With the wording "Immediately" delta would be the correct option as the full sync depending on directory size could take hours... and the delta sync default is every hour. I still count as correct but this is a badly formulated question.
  16. CommanderBigMac 👍 4 Answered B
    While -PolicyType Initial will work, it will take some time. The question specifically says that the new user data needs to be synced immediately, so -PolicyType Delta needs to be used.
  17. GiJoe1987 👍 4 Answered A
    Guys, Initial and Delta will both sync the the required data. Delta is all that is required but Initial will do plus more.
  18. Eltooth 👍 4
    Correct answer - No. - delta is needed for immediate.
  19. ITLearner 👍 3 Answered B
    No Start-ADSyncSyncCycle -PolicyType Initial cmdlet: This PowerShell command is specifically designed to trigger an immediate synchronization of all objects (including users) from your on-premises Active Directory to Azure AD. Hybrid coexistence: Since your environment is configured for hybrid coexistence with DirSync, any changes made in on-premises AD are automatically detected and queued for synchronization with Azure AD. Immediate replication: The -PolicyType Initial flag ensures a complete synchronization, including newly created objects, unlike the default Delta sync which only synchronizes changes since the last run. Therefore, running the Start-ADSyncSyncCycle -PolicyType Initial cmdlet will immediately replicate the newly created user account from your on-premises Active Directory to Azure AD.
  20. RandomNickname 👍 3 Answered B
    As per MS article, take note of manually running; Full sync cycle A full sync cycle includes the following steps: Full Import on all Connectors Full Sync on all Connectors Export on all Connectors It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta. To initiate a full sync cycle, run Start-ADSyncSyncCycle -PolicyType Initial from a PowerShell prompt. Running a full sync cycle can be very time consuming, read the next section to read how to optimize this process. https://learn.microsoft.com/en-us/azure/active-directory/hybrid/connect/how-to-connect-sync-feature-scheduler
  21. Acrious 👍 3 Answered B
    B) B) As usual there are some deterministic things. 1. It says immediately. Initial will not be immediate so therefor it cannot be Initial. yes it will start essentially (immediately), but for all we know there are 100,000 accounts and you are about to replicate it all again 2. It says the User information needs to be done immediately. now I recognize that doing an initial will at some point get to the User information and I get that Initial or Delta will do that, but again, I believe the point they are looking at is, how do we do it "immediately" Not, how do we do it at all. So you have Time: Immediately Accounts: User (the new one) B only meets that to the intent of the question (IMHO)
  22. TheFivePips 👍 3 Answered B
    The Start-ADSyncSyncCycle cmdlet has two policy types: Delta: This policy type performs a delta (or incremental) synchronization, syncing only the changes since the last sync. Initial: This policy type performs a full synchronization, syncing all objects and attributes. To immediately replicate the new user information to Azure AD, the Delta synchronization is typically sufficient because it syncs recent changes. The correct command for this scenario should be: Start-ADSyncSyncCycle -PolicyType Delta Thus, the correct answer is: B. No The -PolicyType Initial performs a full synchronization, which is more extensive than necessary just to sync a new user account.
  23. Mozbius_ 👍 3
    Not sure what to think here... I am preparing for az-104 and followed Microsoft Delivered course in December and beginning of the month to solidify and NEVER did the instructors mentioned anything about Star-ADSyncSyncCycle. It was basically not part of the syllabus nor in the standards labs. They talked about CSV imports though when talking about bulk imports and also AD Connect that's it. So I am not sure what to think. Perhaps the students are expected to expand on what was taught on their own for the exam? Who got this question the latest?
  24. NaoVaz 👍 3 Answered B
    In my opinion the correct answer is B) "No". The "Start-ADSyncSyncCycle -PolicyType Initial" command will do a full synchronization and therefore take quite some time depending on the amount of information being currently existing in the AD. The fastest way to perform a sync and the thing that is nearest with the requested immediate sync is the command "Start-ADSyncSyncCycle -PolicyType Delta", as described here: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler#delta-sync-cycle
  25. GoldBear 👍 3 Answered B
    https://learn.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler It could be that you have an urgent change that must be synchronized immediately, which is why you need to manually run a cycle. If you need to manually run a sync cycle, then from PowerShell run Start-ADSyncSyncCycle -PolicyType Delta.

Reader comments & corrections

No reader corrections yet — spotted an error or have a note? Share it below.

Log in to comment, report an error, or add a note about this question.

Enable SSPR for Entra Identities

S-grade

Assigning Fabric Licenses in Entra ID Free Tenant

S-grade

Which Certificate from Vault1 for WebApp1 TLS?

S-grade

Does Storage Account Encryption Scope Contributor Role Allow Key Regeneration?

S-grade

Practice All AZ-104 Questions

Access 100 questions with complete answers and detailed explanations.

View Full AZ-104 Practice Test →

← Back to AZ-104 Study Guide