The above error occurs typically when you try to install an add-in from the SharePoint Store using the O365 Global administrator account.
- GoTo Office 365 Admin Portal.
- Under Users, Select “Active Users” and Add a user
- Make sure that you choose “SharePoint Administrator” as the role for the new user
- Now try to login to the site using the new user and add the app from the SharePoint Store.
The above had worked for me when I tried to add the Napa developer tool to the Dev site.
1,290 total views, no views today
Some time back, when I was fairly new to Office 365 & SharePoint Online, for the sake of learning I had provisioned a demo site and playing around with it. At that time, I didn’t know the importance of the SharePoint Online root site and started noticing that my SharePoint instance had started to act weird. Upon further investigation found that the root/default site is not an isolated site after all, and that its existence is very important to the overall health of all other sites provisioned in that tenant.
The below are some facts as to why its better to leave the root site “untouched” and leave it in its own pristine condition:
- Do not ever delete the Root site : If you ever are required to delete the site or had accidentally deleted it, all other SharePoint sites in that tenant will cease to work. This is because of the fact that the “default/root” site is used for some kind of authentication mechanism (before allowing users to sign-in to other sites) and that is very important for it to be available at all times.
- Missing Site Settings in the Default/Root Site: In the root site, if you navigate to “Site Settings” you would notice that some of the most common links would have gone missing such as Themes, Composed Looks, Save as Site Template, Delete Site etc., Even though you are the “Global Adminstrator” / “Site Collection Administrator / Owner”, it would still not be available and this is due to the fact that “Custom Scripts” are not enable in Root site”.
- Custom Scripts Not Enabled in Root site: By design Microsoft has turned off the option to run “Custom Scripts” in the default site, for the sake of preventing users from adding scripts in their My Sites, which could have ill effects on the overall health of the tenant. It should also be noted that “My Sites” are dependent on the root site and use the settings as applied on the root site for enforcing it onto itself as well.
- Cannot create a Default/Root site using PowerShell : Microsoft has disabled provisioning root sites in SharePoint Online using Powershell and it can only be created through the “SharePoint Admin Center”.
- At times, when you try to re-provision a root/default site (which you have deleted for some reason), even after you select the “Permanently delete the site collection from the recycle bin and continue“, it might still throw an error saying that the “A site with that name already exists”. In such instances, you simply have to wait for 1 or 2 hours for it to complete its pending activities.
Taking into consideration the above effects, its advisable to create new sites and perform customizations on them, rather to work directly on the root site. Not sure as to why Microsoft documentation doesn’t warn about its effects, but from all practical purpose, its better if we plan the site hierarchy by including a “\sites” or “\teams” in the URL (which gets added when provisioning new sites in the admin center).
2,400 total views, no views today
One of the short-comings of SharePoint Online is its inability to provide an option for SharePoint Administrators to perform/avail a site backup. Too often when we are done with a site and if we wish to have a backup of the site (just in case of restoring it or to create a new site based off on it.. ), its simply not possible in SharePoint Online.
The one other option available is to leverage the “Save as Site Template” option and create a copy of the site template (with/without data), which can then be re-used for provisioning new sub-sites within an existing top level site collection. However, what if we need to provision a new site from the “SharePoint Admin Center” and use that custom site template? (as you would have noticed that the “Provision new Site collection” menu doesn’t offer any option to list/pick any custom Site Template in its UI.)
1,428 total views, no views today