Set-SPOOrgNewsSite - Not a valid site url for organization news site.

%3CLINGO-SUB%20id%3D%22lingo-sub-982997%22%20slang%3D%22en-US%22%3ESet-SPOOrgNewsSite%20-%20Not%20a%20valid%20site%20url%20for%20organization%20news%20site.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-982997%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20migrated%20a%20classic%20publishing%20enabled%20site%20to%20Communication%20Site.%20I%20tried%26nbsp%3Bdisabling%20and%20enabling%20the%20publishing%20feature.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20command%26nbsp%3BSet-SPOOrgNewsSite%20is%20throwing%20the%20below%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20a%20valid%20site%20url%20for%20organization%20news%20site.%20Either%20site%20pages%20feature%20is%20disabled%20or%20publishing%20feature%20is%20enabled%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1496455%22%20slang%3D%22en-US%22%3ERe%3A%20Set-SPOOrgNewsSite%20-%20Not%20a%20valid%20site%20url%20for%20organization%20news%20site.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1496455%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F113593%22%20target%3D%22_blank%22%3E%40Sajith%20G%20H%3C%2FA%3E%26nbsp%3BI%20am%20having%20the%20same%20problem%20-%20not%20a%20valid%20site%20url%20for%20an%20organizational%20news%20site.%26nbsp%3B%20Did%20you%20ever%20figure%20it%20out%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Contributor

I have migrated a classic publishing enabled site to Communication Site. I tried disabling and enabling the publishing feature. 

 

The command Set-SPOOrgNewsSite is throwing the below error.

 

Not a valid site url for organization news site. Either site pages feature is disabled or publishing feature is enabled

2 Replies

@Sajith G H I am having the same problem - not a valid site url for an organizational news site.  Did you ever figure it out?

The same thing happened to me and disabling the SharePoint Server Publishing site feature didn't fix it. It'd be helpful to know if disabling the SharePoint Server Publishing Infrastructure site collection feature would resolve this issue but it's not an option for us.

 

It'd also be great to understand why publishing needs to be disabled for this to work. If Microsoft had any established upcoming plans to decommission the classic experience, that would explain why they'd be discouraging the use of the publishing features which are strongly tied to the classic experience. Clearly, they'd want to steer their clients to the modern experience if that were the current situation. But that's not the case, so requiring the publishing feature at site collection level or even site level makes no sense.