[DOCS-12260] Cloudcraft Azure support #32424
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Preview links (active after the
|
…:DataDog/documentation into aliciathuerk/DOCS-12260-Cloudcraft-Azure merge master
Contributor
|
From the Cloudcraft team, this looks good. I'd just update this part: These diagrams visually represent AWS cloud resources, allowing you to explore and analyze your environments.I'd update it to include Azure instead of mentioning AWS only. |
Contributor
Author
Thanks @jamesponddotco good catch! Just merged that update. |
buraizu
requested changes
Nov 7, 2025
Contributor
buraizu
left a comment
buraizu
left a comment
There was a problem hiding this comment.
Looks good overall, but left a few suggestions and posted some questions.
Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
Contributor
Author
|
Thanks @buraizu ! I incorporated your feedback in these 2 commits: |
buraizu
reviewed
Nov 10, 2025
Contributor
buraizu
left a comment
buraizu
left a comment
There was a problem hiding this comment.
Thanks for applying that feedback! Just reiterated a previous suggestion with some additional context, and I also posted another question about the updated Azure steps
Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
buraizu
approved these changes
Nov 11, 2025
dussault-antoine
pushed a commit
that referenced
this pull request
Nov 13, 2025
* adding Azure support and updating screenshots * updating permissions for Azure * fix TOC snafu * testing commit image * add info on group by and labels * adding back image * updating infra and obsverability images * update SDS image * vuln and ccm * small wording tweak * feedback from James' review * Apply suggestions from Bryce's review Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com> * incorporating feedback * fix spacing * Apply suggestions from code review Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com> * wording tweak --------- Co-authored-by: aliciascott <alicia.scott@datadoghq.com> Co-authored-by: Bryce Eadie <bryce.eadie@datadoghq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Breaks out the prerequisites section into 2 tabs:
Merge instructions
Merge readiness:
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