OneDrive Not Provisioned

Resolve provisioning errors during file migration preprocessing.

Last updated: 2025-01-15 Troubleshooting

The Problem

Error During Preprocessing

OneDrive not provisioned

This error appears during file preprocessing when migrating to OneDrive.

OneDrive Provisioning Process

🔄
Cloudiway
Sends request
📋
Microsoft Queue
Async processing
Processing
Takes time
OneDrive
Ready

Root Cause

Understanding Microsoft's Provisioning

Typically, OneDrive profiles are created automatically when users first access them. During migration preprocessing, Cloudiway sends a programmatic provisioning request to Office 365.

The Critical Detail

This is an asynchronous task - it only queues the request on Microsoft's side. It could take some time to execute.

Why the Error Appears

The error appears if Microsoft hasn't completed the provisioning within 5 minutes. This indicates a bottleneck on Microsoft's end, not a Cloudiway problem.

Solutions

1

Wait for Microsoft Processing

The provisioning requests remain queued and will eventually execute. Cloudiway cannot accelerate this process on the Microsoft side.

Typical wait time: 5-30 minutes, but can be longer during peak periods.

2

Retry Preprocessing

Once Office 365 completes the provisioning request, restart the preprocessing task to finish successfully.

Wait 15-30 minutes, then retry preprocessing for the affected users.

3

User Login Trigger (Fastest)

Ask affected users to log into their OneDrive directly. This triggers immediate profile creation and can resolve the issue faster than waiting for background processing.

  1. 1. User navigates to onedrive.com
  2. 2. User signs in with their Office 365 credentials
  3. 3. OneDrive is provisioned immediately
  4. 4. Retry preprocessing in Cloudiway

Best Approach

For a small number of users, have them log in directly. For many users, wait and retry preprocessing in batches.

Key Takeaway

This delay originates from Microsoft's infrastructure, not the migration tool. The provisioning request is queued and will be processed - it just takes time. Be patient and retry after waiting.

Was this article helpful?

We value your feedback

Help us improve your experience

What would you like to share with us?

Need direct support? Open a ticket