MicrosoftDocs/azure-docs/articles/confidential-computing

Add workload attestation with dm-verity, IMA and CVMs (#321106) * add attesting workload with dm-verity * apply suggestions from the first PR - change filename, fix author gh id * fix title * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> * Update articles/confidential-computing/how-to-attest-linux-workload.md Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com> --------- Co-authored-by: learn-build-service-prod-05[bot] <274429479+learn-build-service-prod-05[bot]@users.noreply.github.com>

Apply Authoring Assistant style suggestions on skr-policy-examples

Docs: cross-link Trusted Launch SKR pattern from SKR concept References

Docs: add Trusted Launch VM (vTPM) SKR policy examples + cross-link pattern

Merge pull request #320234 from kaizentm/eedorenko/skr-noncc-faq-fix Fix: Secure Key Release does not require Confidential Computing (FAQ correction)

Fix: Secure Key Release does not require Confidential Computing (FAQ correction) The FAQ stated SKR cannot be performed with non-confidential-computing offerings. This contradicts the Key Vault secure key release policy grammar, which states a release policy validates any conforming, DigiCert-rooted MAA token independent of compute type. SKR is a Key Vault Premium / Managed HSM data-plane feature; Trusted Launch VMs (Secure Boot + vTPM) produce MAA tokens with secureboot and x-ms-azurevm-attested-pcr-values claims a release policy can gate on. Rewrites FAQ answers 1 and 2 for consistency with the policy-grammar page and bumps ms.date. No other content changes. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

Fix link formatting for Azure Backup documentation

Fix formatting of Azure Backup support note remove en-us

Update Confidential VM overview with Azure Backup info Added information about Azure Backup support for Confidential VMs in public preview.

Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main) (#319622) * Update beekeeperai.md (#128714) * Update beekeeperai.md Updated the confidential computing solution listing. Mary Beth Chalk * Apply suggestions from code review Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Update beekeeperai.md --------- Co-authored-by: Regan Downer <v-rdowner@microsoft.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> * Remove outdated Preview status for Layer 4 proxy (#128704) The Layer 4 proxy for TLS and TCP protocols is now generally available. This change removes the outdated "in Preview" wording to reflect the current availability status of the feature. * Revise endorsed images and kernel versions for MANA (#128721) Updated the list of endorsed images and minimum recommended kernels for MANA-enabled SKUs, adding new distributions and versions. --------- Co-authored-by: learn-build-service-prod[bot] <113403604+learn-build-service-prod[bot]@users.noreply.github.com> Co-authored-by: chalkatx <chalkatx@gmail.com> Co-authored-by: Regan Downer <v-rdowner@microsoft.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Co-authored-by: Inyoung <inyoungchoi26@gmail.com> Co-authored-by: Denis Salamanca <salafara2@gmail.com>

docs: retire ADF Workflow Orchestration Manager content (#319180)

Removing my name from docs before retirement. (#317491)

Update ACC hero slide, video re-org text and metadata update (#316987) * Update ACC hero slide asset and metadata updated hero slide with current ACC-enabled services * Revise ACC overview: rewrite for clarity, remove SGX, update video and author * Update confidential computing TOC comment: align TOC with latest overview updates * Update SFI references to 2025 progress reports comment: replace 2024 links with April 2025 and November 2025 Secure Future Initiative progress reports * Remove ONNX Runtime from supplementary offerings comment: trim supplementary offerings list in ACC overview * Mark Azure Integrated HSM as GA comment: update supplementary offerings text to reflect general availability * Switch What's New video to Build-hosted source comment: replace removed YouTube video with Build session media and target the confidential computing segment --------- Co-authored-by: Simon Gallagher <sgallagher@microsoft.com>

Merge pull request #317310 from linuxelf001/patch-53 Add note and PowerShell script for MAA endpoint

Add note and PowerShell script for MAA endpoint Added a note about MAA endpoint availability and provided a PowerShell script to retrieve the regional MAA endpoint URL as a workaround.

Add note and script for MAA endpoint retrieval Added a note regarding MAA endpoint availability in new regions and provided a PowerShell script to retrieve the regional MAA endpoint URL.

Update confidential-clean-rooms.md Ensured that ACCR for analytics is replaced with multiparty analytics for ACCR throughout the doc as per marketing recommendation.

Update section title for Azure Confidential Clean Rooms Conforming to the guidance from Marketing

Remove contact details for analytics solution inquiries Removed contact information for the Azure Confidential Clean Rooms product team from the document.

Refine privacy controls explanation in documentation