Skip to content

Commit 5a92499

Browse files
Merge pull request #2622 from MicrosoftDocs/main
Auto Publish – main to live - 2026-03-16 05:00 UTC
2 parents cc1a19f + 32a263c commit 5a92499

20 files changed

Lines changed: 79 additions & 79 deletions

articles/attestation/tpm-attestation-sample-policies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -71,7 +71,7 @@ c:[type=="srtmDrtmEventPcr", issuer=="AttestationPolicy"] => add(type="Bitlocker
7171
[type=="BitlockerStatus", issuer=="AttestationPolicy"] => issue(type="BitlockerStatus", value=true);
7272
![type=="BitlockerStatus", issuer=="AttestationPolicy"] => issue(type="BitlockerStatus", value=false);
7373
74-
// Elam Driver (windows defender) Loaded
74+
// Elam Driver (Microsoft Defender) Loaded
7575
c:[type=="boolProperties", issuer=="AttestationPolicy"] => add(type="elamDriverLoaded", value=JsonToClaimValue(JmesPath(c.value, "[*].EVENT_LOADEDMODULE_AGGREGATION[] | [? EVENT_IMAGEVALIDATED == `true` && (equals_ignore_case(EVENT_FILEPATH, '\\windows\\system32\\drivers\\wdboot.sys') || equals_ignore_case(EVENT_FILEPATH, '\\windows\\system32\\drivers\\wd\\wdboot.sys'))] | @ != `null`")));
7676
[type=="elamDriverLoaded", issuer=="AttestationPolicy"] => issue(type="ELAMDriverLoaded", value=true);
7777
![type=="elamDriverLoaded", issuer=="AttestationPolicy"] => issue(type="ELAMDriverLoaded", value=false);

articles/confidential-ledger/manage-azure-ad-token-based-users.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ ledger_client = ConfidentialLedgerClient(
5555

5656
# Add a user with the contributor role
5757
# Other supported roles are Contributor and Administrator
58-
user_id = "Azure AD object id of the user"
58+
user_id = "Microsoft Entra ID object id of the user"
5959
user = ledger_client.create_or_update_user(
6060
user_id, {"assignedRole": "Contributor"}
6161
)
@@ -98,7 +98,7 @@ internal class ACLUserManagement
9898
// The DefaultAzureCredential will use the current Azure context to authenticate to Azure
9999
var ledgerClient = new ConfidentialLedgerClient(new Uri("https://contoso.confidential-ledger.azure.com"), new DefaultAzureCredential());
100100
101-
string userId = "Azure AD object id of the user";
101+
string userId = "Microsoft Entra ID object id of the user";
102102
103103
// Add the user with the Reader role
104104
// Other supported roles are Contributor and Administrator
@@ -206,7 +206,7 @@ public class CreateOrUpdateUserSample {
206206
// Other supported roles are Contributor and Administrator
207207
BinaryData userDetails = BinaryData.fromString("{\"assignedRole\":\"Reader\"}");
208208
RequestOptions requestOptions = new RequestOptions();
209-
String userId = "Azure AD object id of the user";
209+
String userId = "Microsoft Entra ID object id of the user";
210210
Response<BinaryData> response = confidentialLedgerClient.createOrUpdateUserWithResponse(userId,
211211
userDetails, requestOptions);
212212

@@ -277,8 +277,8 @@ export async function main() {
277277
new DefaultAzureCredential()
278278
);
279279

280-
// Azure AD object id of the user
281-
const userId = "Azure AD Object id"
280+
// Microsoft Entra ID object id of the user
281+
const userId = "Microsoft Entra ID Object id"
282282

283283
// Other supported roles are Reader and Contributor
284284
const createUserParams: CreateOrUpdateUserParameters = {

articles/confidential-ledger/quickstart-template.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
2-
title: Create an Microsoft Azure confidential ledger by using Azure Resource Manager template
3-
description: Learn how to create an Microsoft Azure confidential ledger by using Azure Resource Manager template.
2+
title: Create a Microsoft Azure confidential ledger by using Azure Resource Manager template
3+
description: Learn how to create a Microsoft Azure confidential ledger by using Azure Resource Manager template.
44
services: azure-resource-manager
55
author: msmbaldwin
66
ms.service: azure-confidential-ledger
@@ -10,7 +10,7 @@ ms.author: mbaldwin
1010
ms.date: 04/14/2025
1111
---
1212

13-
# Quickstart: Create an Microsoft Azure confidential ledger with an ARM template
13+
# Quickstart: Create a Microsoft Azure confidential ledger with an ARM template
1414

1515
[Microsoft Azure confidential ledger](overview.md) is a new and highly secure service for managing sensitive data records. This quickstart describes how to use an Azure Resource Manager template (ARM template) to create a new ledger.
1616

articles/confidential-ledger/quickstart-terraform.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ In this quickstart, you create an Azure resource group and a confidential ledger
2424
> * Retrieve the current Azure client configuration.
2525
> * Generate a random string for the Azure confidential ledger name.
2626
> * Create an Azure confidential ledger with the generated name and assign it to the resource group.
27-
> * Assign an Azure AD based service principal to the confidential ledger.
27+
> * Assign a Microsoft Entra ID based service principal to the confidential ledger.
2828
> * Tag the confidential ledger as an example.
2929
> * Output the resource group name, confidential ledger name, confidential ledger type, and confidential ledger role name.
3030
> * Specify the required version of Terraform and the required providers.

articles/dedicated-hsm/overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ Azure Dedicated HSM is most suitable for “lift-and-shift” scenarios that req
6565

6666
### Not a fit
6767

68-
Azure Dedicated HSM is not a good fit for the following type of scenario: Microsoft cloud services that support encryption with customer-managed keys (such as Azure Information Protection, Azure Disk Encryption, Azure Data Lake Store, Azure Storage, Azure SQL Database, and Customer Key for Office 365) that are not integrated with Azure Dedicated HSM.
68+
Azure Dedicated HSM is not a good fit for the following type of scenario: Microsoft cloud services that support encryption with customer-managed keys (such as Azure Information Protection, Azure Disk Encryption, Azure Data Lake Store, Azure Storage, Azure SQL Database, and Customer Key for Microsoft 365) that are not integrated with Azure Dedicated HSM.
6969

7070
> [!NOTE]
7171
> Customers must have an assigned Microsoft Account Manager and meet the monetary requirement of five million ($5M) USD or greater in overall committed Azure revenue annually to qualify for onboarding and use of Azure Dedicated HSM.

articles/defender-for-cloud/alerts-resource-manager.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -118,7 +118,7 @@ This article lists the security alerts you might get for Resource Manager from M
118118

119119
**Severity**: High
120120

121-
### **PowerZure exploitation toolkit used to elevate access from Azure AD to Azure**
121+
### **PowerZure exploitation toolkit used to elevate access from Microsoft Entra ID to Azure**
122122

123123
(ARM_PowerZure.AzureElevatedPrivileges)
124124

articles/defender-for-cloud/defender-for-cloud-glossary.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ Shared access signature that provides secure delegated access to resources in yo
275275

276276
### **SaaS**
277277

278-
Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet. Common examples are email, calendaring, and office tools (such as Microsoft Office 365). SaaS provides a complete software solution that you purchase on a pay-as-you-go basis from a cloud service provider.[What is SaaS?](https://azure.microsoft.com/resources/cloud-computing-dictionary/what-is-saas/).
278+
Software as a service (SaaS) allows users to connect to and use cloud-based apps over the Internet. Common examples are email, calendaring, and office tools (such as Microsoft 365). SaaS provides a complete software solution that you purchase on a pay-as-you-go basis from a cloud service provider.[What is SaaS?](https://azure.microsoft.com/resources/cloud-computing-dictionary/what-is-saas/).
279279

280280
### **Secure Score**
281281

articles/defender-for-cloud/defender-for-sql-scan-results.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -114,7 +114,7 @@ Azure Logic Apps is a low-code or no-code cloud-based service that provides you
114114

115115
You can use [these instructions](https://github.com/Azure/Microsoft-Defender-for-Cloud/tree/main/Workflow%20automation/Notify-SQLVulnerabilityReport), to learn how to use Logic Apps to automate email notifications using an example template.
116116

117-
This example Logic App template automates a weekly email report that summarizes the vulnerability scan results for every database from a selected list of servers. After you deploy the template, you must authorize the Office 365 connector to generate a valid access token to authenticate your credentials.
117+
This example Logic App template automates a weekly email report that summarizes the vulnerability scan results for every database from a selected list of servers. After you deploy the template, you must authorize the Microsoft 365 connector to generate a valid access token to authenticate your credentials.
118118

119119
The recipients receive emails with the findings of the scan results.
120120

articles/defender-for-cloud/recommendations-reference-ai.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ This recommendation replaces the old recommendation *Cognitive Services should u
120120

121121
### Azure Machine Learning Computes should have local authentication methods disabled (Preview)
122122

123-
**Description & related policy**: Disabling local authentication methods improves security by ensuring that Machine Learning Computes require Azure Active Directory identities exclusively for authentication. For more information, see [Azure Policy Regulatory Compliance controls for Azure Machine Learning](/azure/machine-learning/security-controls-policy).
123+
**Description & related policy**: Disabling local authentication methods improves security by ensuring that Machine Learning Computes require Microsoft Entra ID identities exclusively for authentication. For more information, see [Azure Policy Regulatory Compliance controls for Azure Machine Learning](/azure/machine-learning/security-controls-policy).
124124

125125
**Severity**: Medium
126126

articles/defender-for-cloud/recommendations-reference-app-services.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -115,23 +115,23 @@ Using the latest Python version for API apps is recommended to benefit from secu
115115
### Managed identity should be used in API apps
116116

117117
**Description**: For enhanced authentication security, use a managed identity.
118-
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Azure AD and using it to obtain Azure Active Directory (Azure AD) tokens.
118+
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Microsoft Entra ID and using it to obtain Microsoft Entra ID (Microsoft Entra ID) tokens.
119119
(Related policy: [Managed identity should be used in your API App](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2fc4d441f8-f9d9-4a9e-9cef-e82117cb3eef)).
120120

121121
**Severity**: Medium
122122

123123
### Managed identity should be used in function apps
124124

125125
**Description**: For enhanced authentication security, use a managed identity.
126-
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Azure AD and using it to obtain Azure Active Directory (Azure AD) tokens.
126+
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Microsoft Entra ID and using it to obtain Microsoft Entra ID (Microsoft Entra ID) tokens.
127127
(Related policy: [Managed identity should be used in your Function App](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f0da106f2-4ca3-48e8-bc85-c638fe6aea8f)).
128128

129129
**Severity**: Medium
130130

131131
### Managed identity should be used in web apps
132132

133133
**Description**: For enhanced authentication security, use a managed identity.
134-
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Azure AD and using it to obtain Azure Active Directory (Azure AD) tokens.
134+
On Azure, managed identities eliminate the need for developers to have to manage credentials by providing an identity for the Azure resource in Microsoft Entra ID and using it to obtain Microsoft Entra ID (Microsoft Entra ID) tokens.
135135
(Related policy: [Managed identity should be used in your Web App](https://portal.azure.com/#blade/Microsoft_Azure_Policy/PolicyDetailBlade/definitionId/%2fproviders%2fMicrosoft.Authorization%2fpolicyDefinitions%2f2b9ad585-36bc-4615-b300-fd4435808332)).
136136

137137
**Severity**: Medium

0 commit comments

Comments
 (0)