Skip to main content

OneDrive Can't Add Your Folder Right Now!

This post is nothing related to servers. I post that since I couldn't find anything on the internet about this issue. This "OneDrive Can't Add Your Folder" spent me quite a while to figure it out. I only found an article talks about IRM after I figured the issue out. So I think it's maybe valuable to document that. I re-installed the testing machine by different OS versions several times. It's just happened suddenly. My OneDrive cannot sync any files. I upgraded the client to the latest version but no luck.

The error message I got initially was:

We can't sync your OneDrive - xxx

Following these steps to fix the problem:

1. Go to, click the Settings icon in the top-right, then click "Site settings".

2. Under "Site Administration", click "Site libraries and lists".

3. Click "Customise Documents".

4. Click "Information Rights Management" and clear the checkbox.

Then I upgraded OneDrive client, re-installed office, re-installed OS, and enabled full permission to my O365 account on OneDrive folders. I also tracked my OneDrive posting data by a nice free tool Fiddler. There are error keywords related to "IRM" that don't support in Fiddler when I connected OneDrive to my O365 account. Then I uninstalled OneDrive and installed latest version of it. Now I got following error message when sign in my O365 account in OneDrive.

Sorry, OneDrive can't add your folder right now

Please contact support.

I eventually figured it out when I was troubleshooting other software issues. The reason is the "Information Rights Management" (IRM) feature was enabled on my O365 account. It restricts file synchronization on unauthorized computers when I log in to a computer with my domain account (it's also the O365 account). I checked my computer domain account in "Active Directory Users and Computers". I noticed that the "Managed By" of the computer was blank. The OneDrive issue resolved as soon as I set it to my domain account.
Here is a good article to explain what's IRM and how it affects OneDrive.

Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $