Site Swap issues (Invoke-SPOSiteSwap)
Hello All, I just ran "Invoke-SPOSiteSwap" and get some issues so I have some questions: 1. Scenario The script worked fine (Moved the Source to targeted and create the Archive) 1.1 I moved the xxx.sharepoint.com/sites/Public to root site xxx.sharepoint.com 1.2 It takes ~1 hour 1.3 I moved root site xxx.sharepoint.com to xxx.sharepoint.com/sites/archive 1.4 Site permission and files are moved correctly 1.5 In the article said we need to manually backup the Featured links because will not be displayed after performing the swap, but I am able to see the same Featured links in the xxx.sharepoint.com/_layouts/15/sharepoint.aspx 2. Issues: 2. Before running the script in Admin center I had root site "xxx.sharepoint.com" and "xxx.sharepoint.com/sites/Public" I was expecting to have "xxx.sharepoint.com" and "xxx.sharepoint.com/sites/Archive" after running the script. But here is the big issue: I still have the "xxx.sharepoint.com/sites/Public" and it's giving me "Sorry, something went wrong" also there is no "xxx.sharepoint.com/sites/Archive" in the admin center. Please let me know if you need more information. Alireza
Any Alternative for Test, Dev, UAT for SharePoint Online to test solution before taking to live
Dear All, We are having huge Content DB of SharePoint 2013 and we convinced the features of SharePoint Online and it's advantages and our client had given the signal to move all the solutions for SharePoint Online. As we all knew for SharePoint On-premise solutions we do have Dev, TEST , UAT Environments were we implement and validate the requirements before we take ahead to production But how do we test our solution on SharePoint Online including permissions and all other features(Permissions).Any Alternative for Test, Dev, UAT for SharePoint Online to test solution before taking to live
Dear All, We are having huge Content DB of SharePoint 2013 and we convinced the features of SharePoint Online and it's advantages and our client had given the signal to move all the solutions for SharePoint Online. As we all knew for SharePoint On-premise solutions we do have Dev, TEST , UAT Environments were we implement and validate the requirements before we take ahead to production But how do we test our solution on SharePoint Online including permissions and all other features(Permissions).
Want to disable SharePoint non-owners to invite new users
In the Office 365 SharePoint admin center under the site collections section I open the sharing screen for a site collection. There is an option to "Turn off sharing for non-owners on all sites in this site collection." This effectively unchecks all the boxes in the Access request settings page of all the sites in the site collection. However, I just found that they can still be re-checked by the site owners of the sites, also at subsite level, even after this. This means that what initially seems like a de-activation of the option to share the sites by non-owners is nothing but a reset of the Access request settings on the sites. This is disturbing and puzzling as you would think changing such a key setting for the site collection in the SharePoint admin centre would have a permanent effect. Does anyone know if this is the intention or if there is an option to completely disable the option that I did not catch? Fig.1 shows the settings prior to turning off for the site collection. Fig.2 after. Then Fig.3 shows it being possible to activate at subsite level anyway - which actually resets the setting in the admin center also back to what is shown in Fig.1.Continuous integration and deployment for your SharePoint Framework solutions
New article on my blog how to configure on Visual Studio Team Services the continuous integration and deployment for a SharePoint Framework solution, I hope it's helpful. http://www.delucagiuliano.com/continuous-integration-and-deployment-for-your-sharepoint-framework-solutions/
