You ever get that itch? The one where you’re staring at a crusty old SharePoint site called secretproject-x and think:
“This name is a lie. The project isn’t secret. It’s not even cool. It’s basically a glorified folder with bad permissions and a files no one updates.”
So I opened up my trusty PowerShell console, cracked my knuckles like some kind of digital necromancer, and ran:
Start-SPOSiteRename -Identity <OLD URL> -NewSiteUrl <NEW URL> -ValidationOnlyNote the -ValidationOnly parameter. That’s the “don’t actually burn it down yet” switch.
It’s me gently asking my SharePoint tenant,
“Hey, if I were to pull the trigger and rename this glorified dumpster fire… would you scream? Or would you quietly accept your new identity like a good little cloud service?”
Let me tell you: SharePoint didn’t scream. No red text. No errors. Just a smug little message that basically said: “Yeah, you could rename this site. I won’t stop you.”
Which is both comforting and terrifying. Like finding out your cat knows how to open the fridge but just… hasn’t. Yet.
Of course, I didn’t go through with it today. I’m not that reckless. It’s friday ater all.
There are bookmarks out there. Teams integrations. Random Flow automations duct-taped by someone who left the company in 2001.
So today, we validate. Tomorrow, we rename. Or maybe we don’t. Maybe we just sit on this command for another two weeks, like a cartoon character holding a lit match in a ACME fireworks factory.
Either way, secretproject-x’s days are numbered. projectdumpsterfire-y is coming.
And yes, I already regret that name too.
k9xm8f