Hello Stephen,
Welcome to Microsoft Q&A, This usually happens when the workspace setup doesn’t align with Sentinel’s onboarding requirements or there's a temporary issue on the platform side. According to Microsoft’s official documentation, here’s what to check:
Make sure the workspace is in a supported region and isn’t already connected to another Sentinel instance.
Confirm your Azure subscription has the right permissions: Owner or Contributor on the workspace and Reader on the resource group.
If everything looks fine, try again after a short wait—sometimes the error clears up on its own.
If the problem persists, consider removing Sentinel from the workspace (if partially added) and re-onboarding it from scratch.
Reference:
If this resolves your question, please accept the answer.
Luis