Ok, so the missing role is the Azure Security Administrator role and this was not active and kept getting these errors.
Copilot for Security portal returns error 400
After creating the capacity on the Azure portal, I navigate to https://securitycopilot.microsoft.com to finish the setup, but encountered the following error.
I am already have the owner RBAC to the subscription it exists in so permission shouldn't be an issue.
Appreciate any help and/or advice, thank you in advance.
4 answers
Sort by: Most helpful
-
-
Jesse Jaatinen 11 Reputation points
2024-11-04T17:45:29.2666667+00:00 The Security Administrator role must be active. Once it is all works
-
Bob Alberti 0 Reputation points
2025-02-20T19:50:15.65+00:00 Why is it acceptable that this service generates a meaningless and misspelled error code and we're all stuck figuring it out? I got stuck on this yesterday and had to leave off working on it, and overnight it ate $140 because I'm still learning how to set it up and haven't gotten to how to turn it off.
-
Guillaume Berthier 36 Reputation points
2025-03-12T15:11:54.85+00:00 Hi @Anonymous , @Anonymous , I got the same error message "Service return unhandle error code:400" while trying to access https://securitycopilot.microsoft.com/ ; I found out that it's just because our Tenant Global Admin never configured it.
For that you have to provision in Azure a capacity in Security Compute Units (SCU) (to run Security Copilot workloads). When done the Global Admin will have to select the SCU has shown below