Update & reorganize CloudSec disabling docs

[janine-c]

What does this PR do? What is the motivation?

• Updates existing instructions to disable Cloud Security
• Reorganizes these instructions to make them easier to find

Merge instructions

Please wait to merge until we have the okay from @daniel-pahor and team. Thank you for sharing your expertise with us, Daniel!

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/janine.chan/cloudsec-deactivation/security/cloud_security_management/setup/agentless_scanning/enable
• https://docs-staging.datadoghq.com/janine.chan/cloudsec-deactivation/security/cloud_security_management/setup/cloud_integrations

[daniel-pahor]

Nice! This is really great. A couple of comments.

And one more thing, I see "Azure Subscription" is still mentioned three times in this doc and "Google Cloud Project" once - my bad I didn't mention we wanted it changed throughout the doc not just the de-activation part. Can we rename them to "account" too?

[janine-c]

Thank you, @daniel-pahor! Great catch with the remaining outdated terminology; I've just pushed a change to update that.

If Slack says I'm OOO the next time you're able to take a look:

• If you need any additional changes, feel free to post in #documentation if you need any help (or just commit directly to this PR if you prefer)
• When it's ready to publish:
  1. Remove the WORK IN PROGRESS label so the PR goes into the queue for one of my colleagues to review
  2. Select the Ready for merge checkbox at the top of the PR so the interrupt handler on duty knows they can merge it when they approve it
  3. Watch for the published changes an hour or so after merging (it takes about that long to fully rebuild the docs site)

If you need anything else, #documentation is the place to go, and I'll be back on Wednesday too 🙂 Thank you for being so helpful and thorough with this task; you've really been an ideal collaborator!

[daniel-pahor]

Thanks @janine-c enjoy your break. I fixed some nits then followed your instructions above. Thank you.

[iadjivon]

Suggested change

	1. Toggle **Vulnerability Scanning** to the on position.
	1. Toggle **Vulnerability Scanning** to the on position.

non-blocking, but in this case would emphasizing the "ON" in "on position" be helpful? I guess there's no "ON" and "OFF" as words in the UI, so maybe a different way than capitalizing?