New support for # and % in SharePoint Online and OneDrive for Business


In the upcoming weeks, we’ll be shipping support for # and % as supported characters in file and folder names across document libraries in SharePoint Online and OneDrive for Business.  This will allow people to create, store, and sync files containing # and % characters whether those characters are used as a prefix or suffix to the file or folder name.  # and % will be limited to use in file names in addition to SharePoint Online and OneDrive for Business document libraries and related folders. 


More information here:



24 Replies

Thanks! I will share this with our engineering team :)

Hooray at last... all of my clients in the finance sector will be very happy with this... I've been promising them it's coming for a long time now!

Thats great as we are just planning our migration from Egnyte to OneDrive and have just come across this limitation, how will we know when it is now an option?
Just seen on the other site that we still have a long wait then...

H2 CY2017 for existing Office 365 Tenants

Great news. I enabled this, this morning and it looks like it's working for us.

How did you do it?

I just want to make sure as support have been no help for me so far and all that happens for me is that when I run the Get-SPOTenant/Set-SPOTenant it says that is not a recognized name of a cmdlet
Scrap that I found on the comments on the article the following script seems to work just need to give it some time.

$userCredential = Get-Credential -UserName $adminUPN -Message "Type the password."
Connect-SPOService -Url
Set-SPOTenant -SpecialCharactersStateInFileFolderNames Allowed
Yeap, it needs some time what it's normal because you are modifying a tenant setting :)
Fingers crossed it works for us then

Out of interest have any of you heard about them extending the path length as per the other post on here?

I don't want to spend ages reducing path lengths so that we can migrate to then find it gets extended soon afterwards anyway.

HI Peter,


Tenant updattion took 2 hrs.


Now we are able to sync items which contains # and % characters.


I believe 30-40% synchronization issue automatically resolved by allowing thes characters.

Other than long paths though I assume

I think long path is also resolved by increasing from 256 to 400 character, not sure it is reolled out or not. I posted in another discussion, and waiting for confirmation someone from microsoft. Here is the discussion thread



We have extended the path to 400 characters


When will that hit our systems then? Just wanted to check as I am currently trying to sync and it keeps complaining about path length still.

It's rollout out now. It usually takes 30-45 days to hit all tenants

@Peter Longley wrote:

When will that hit our systems then? Just wanted to check as I am currently trying to sync and it keeps complaining about path length still.


Okay thanks for confirming. So we do not need to run anything like we did for the special characters change?

Hi Stephen,

Is there any announcement published on 400 characters limit?

Hi Stephen,


Which limit exactly is upgraded? Apparently there are limits tot the local storage as well as to the online storage. Are they both increased?




Are there any other limits (eg length of file name as opposed to length of path)?