Confusing Access Denied and managing Navigation Office 365

Confusing Access Denied and managing Navigation Office 365

Not that long ago Microsoft started to roll out the option to disable custom scripts in your Office 365 Tenant. You can read up on it in the article Turn scripting capabilities on and off on the office.com site. While it is a great way to prevent users from adding custom scripts it disables some of the good stuff that was available for your administrators. However it is worth thinking of the options as it will disable sandboxed solutions, something you cannot ‘enforce’ otherwise.

From within the SharePoint Management screen you can find the settings in the settings tab.

Scripting Capability settings

An interesting note is that by default these settings are now rolled out as disabled. Thus preventing users from running custom script. All new tenants will have this option checked. With the option disabled a minor bug (or undocumented consequence) will occur. It turns out that you can no longer change the navigation mode of your site.

So imagine that you have a publishing site that uses the Structural Navigation and you decide to switch to Managed Navigation (or the other way around). Normally you would navigate to the Navigation Settings page, something you can still do, however when you try to save your changes you will end up with an access denied. The access denied page will only provide you with the following:

Access Denied with custom script disabled

It turns out that the something on the page requires the scripting capabilities and that it can no longer be executed. So while custom script are disabled you will not be able to change the navigation settings, nor add new links or headings if you have the structural navigation selected. You can add new links to the quick launch if it is set to structural navigation by clicking the edit link. Any changes committed through that process are saved and visible for all your users.

Only changes that are set through the ‘navigation’ settings that are accessible through Site Settings – Navigation will fail once you click the OK to commit and save the changes. The only option currently available is to enable the custom scripts again. Within 24 hours you will be able to change the navigations as you would have expected.

There are 7 comments for this article
  1. Rob at 10:12

    Just wanted to say thank you, I've been fighting with this problem for a week and your solution fixed the issue.

  2. Sibila Thompson at 05:04

    I have the same issue and it is not resolved by turning scripting on. On the main site I get error messages but am nevertheless able to edit the navigation. However, on sub-sites, I cannot switch from "inherit navigation" to "managed navigation". Any thoughts would be much appreciated

    • Albert-Jan Schot at 14:15

      I haven't seen that problem, but there is always a first. Is the option clickable or is it grayed out? Are the publishing features enabled correctly? You could try to disable and enable them again just to make sure they are.

      • Sibila Thompson at 00:34

        The "Allow users to run custom script.." is clickable. I've tried turning it off and on again. May take a while to see if that has any effect. And yes, publishing is enabled correctly.

        I'm becoming more and more convinced that this has something to do with the fact that we have subscribed to Office365 through GoDaddy. Have lately been reading about so many people having issues with admin functions that are either simply missing or that don't work. Am seriously thinking about moving from GoDaddy to Microsoft directly. It's just an additional cost, as well as the hassle.

        Thanks for your response though! If the off/on works, I'll let you know.

Leave a Reply