Skip to content

Commit 3d5c869

Browse files
committed
Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into rolyon-rbac-roles-refactor-anchors
2 parents 687f71c + 68c4d8b commit 3d5c869

File tree

11 files changed

+148
-133
lines changed

11 files changed

+148
-133
lines changed

articles/ai-services/speech-service/personal-voice-create-consent.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ To add user consent to the personal voice project, you provide the prerecorded c
2222

2323
You need an audio recording of the user speaking the consent statement.
2424

25-
You can get the consent statement text for each locale from the text to speech GitHub repository. See [SpeakerAuthorization.txt](https://github.com/Azure-Samples/Cognitive-Speech-TTS/blob/master/CustomVoice/script/English%20(United%20States)_en-US/SpeakerAuthorization.txt) for the consent statement for the `en-US` locale:
25+
You can get the consent statement text for each locale from the text to speech GitHub repository. See [verbal-statement-all-locales.txt](https://github.com/Azure-Samples/Cognitive-Speech-TTS/blob/master/CustomVoice/script/verbal-statement-all-locales.txt) for the consent statement. Below is a sample for the `en-US` locale:
2626

2727
```
2828
"I [state your first and last name] am aware that recordings of my voice will be used by [state the name of the company] to create and use a synthetic version of my voice."

articles/azure-netapp-files/azure-netapp-files-network-topologies.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ Azure NetApp Files volumes are designed to be contained in a special purpose sub
7373
* West US 2
7474
* West US 3
7575

76-
<a name="regions-edit-network-features"></a>The option to *[edit network features for existing volumes (preview)](configure-network-features.md#edit-network-features-option-for-existing-volumes)* is supported for the following regions:
76+
<a name="regions-edit-network-features"></a>The option to *[edit network features for existing volumes](configure-network-features.md#edit-network-features-option-for-existing-volumes)* is supported for the following regions:
7777

7878
* Australia Central
7979
* Australia Central 2

articles/azure-netapp-files/configure-network-features.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ This section shows you how to set the network features option when you create a
7373

7474
[ ![Screenshot that shows the Volumes page displaying the network features setting.](./media/configure-network-features/network-features-volume-list.png)](./media/configure-network-features/network-features-volume-list.png#lightbox)
7575

76-
## <a name="edit-network-features-option-for-existing-volumes"></a> Edit network features option for existing volumes (preview)
76+
## Edit network features option for existing volumes
7777

7878
You can edit the network features option of existing volumes from *Basic* to *Standard* network features. The change you make applies to all volumes in the same *network sibling set* (or *siblings*). Siblings are determined by their network IP address relationship. They share the same NIC for mounting the volume to the client or connecting to the SMB share of the volume. At the creation of a volume, its siblings are determined by a placement algorithm that aims for reusing the IP address where possible.
7979

articles/azure-netapp-files/whats-new.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ Azure NetApp Files is updated regularly. This article provides a summary about t
1616

1717
## February 2024
1818

19+
* The [Standard network features - Edit volumes](configure-network-features.md#edit-network-features-option-for-existing-volumes) feature is now generally available (GA).
20+
21+
You are no longer required to register when you edit the network features option of existing volumes from Basic to Standard network features.
22+
1923
* [Large volumes (Preview) improvement:](large-volumes-requirements-considerations.md#requirements-and-considerations) volume size increase beyond 30% default limit
2024

2125
For capacity and resources planning purposes the Azure NetApp Files large volume feature has a [volume size increase limit of up to 30% of the lowest provisioned size](large-volumes-requirements-considerations.md#requirements-and-considerations). This volume size increase limit is now adjustable beyond this 30% (default) limit via a support ticket. For more information, see [Resource limits](azure-netapp-files-resource-limits.md).

articles/defender-for-cloud/agentless-malware-scanning.md

Lines changed: 15 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -37,9 +37,22 @@ You can learn more about [agentless machine scanning](concept-agentless-data-col
3737
> [!IMPORTANT]
3838
> Security alerts appear on the portal only in cases where threats are detected on your environment. If you do not have any alerts it may be because there are no threats on your environment. You can [test to see if the agentless malware scanning capability has been properly onboarded and is reporting to Defender for Cloud](enable-agentless-scanning-vms.md#test-the-agentless-malware-scanners-deployment).
3939
40-
On the Security alerts page, you can [manage and respond to security alerts](managing-and-responding-alerts.md). You can also [review the agentless malware scanner's results](managing-and-responding-alerts.md#review-the-agentless-scans-results). Security alerts can also be [exported to Sentinel](export-to-siem.md).
40+
### Defender for Cloud security alerts
4141

42-
:::image type="content" source="media/agentless-malware-scanning/agentless-alerts-results.png" alt-text="Screenshot of the Alerts page in Defender for Cloud that shows how the agentless scan's results appear on that page." lightbox="media/agentless-malware-scanning/agentless-alerts-results.png":::
42+
When a malicious file is detected, Microsoft Defender for Cloud generates a [Microsoft Defender for Cloud security alert](alerts-overview.md#what-are-security-alerts). To see the alert, go to **Microsoft Defender for Cloud** security alerts.
43+
The security alert contains details and context on the file, the malware type, and recommended investigation and remediation steps. To use these alerts for remediation, you can:
44+
45+
1. View [security alerts](https://portal.azure.com/#view/Microsoft_Azure_Security/SecurityMenuBlade/~/7) in the Azure portal by navigating to **Microsoft Defender for Cloud** > **Security alerts**.
46+
1. [Configure automations](workflow-automation.md) based on these alerts.
47+
1. [Export security alerts](alerts-overview.md#exporting-alerts) to a SIEM. You can continuously export security alerts Microsoft Sentinel (Microsoft’s SIEM) using [Microsoft Sentinel connector](../sentinel/connect-defender-for-cloud.md), or another SIEM of your choice.
48+
49+
Learn more about [responding to security alerts](../event-grid/custom-event-quickstart-portal.md#subscribe-to-custom-topic).
50+
51+
### Handling possible false positives
52+
53+
If you believe a file is being incorrectly detected as malware (false positive), you can submit it for analysis through the [sample submission portal](/microsoft-365/security/intelligence/submission-guide). The submitted file will be analyzed by Defender's security analysts. If the analysis report will indicate that the file is in fact clean, then the file will no longer trigger new alerts from now on.
54+
55+
Defender for Cloud allows you to [suppress false positive alerts](alerts-suppression-rules.md). Make sure to limit the suppression rule by using the malware name or file hash.
4356

4457
## Next steps
4558

articles/defender-for-cloud/enable-agentless-scanning-vms.md

Lines changed: 29 additions & 44 deletions
Original file line numberDiff line numberDiff line change
@@ -167,51 +167,36 @@ The alert `MDC_Test_File malware was detected (Agentless)` will appear within 24
167167

168168
1. Execute the following script.
169169

170-
```powershell
171-
# virus test string
172170

173-
$TEST_STRING = '$$89-barbados-dublin-damascus-notice-pulled-natural-31$$'
174-
175-
176-
177-
# File to be created
178-
179-
$FILE_PATH = "C:\temp\virus_test_file.txt"
180-
181-
182-
183-
# Write the test string to the file without a trailing newline
184-
185-
[IO.File]::WriteAllText($FILE_PATH, $TEST_STRING)
186-
187-
188-
189-
# Check if the file was created and contains the correct string
190-
191-
if (Test-Path -Path $FILE_PATH) {
192-
193-
$content = [IO.File]::ReadAllText($FILE_PATH)
194-
195-
if ($content -eq $TEST_STRING) {
196-
197-
Write-Host "Test file created and validated successfully."
198-
199-
}
200-
201-
else {
202-
203-
Write-Host "Test file does not contain the correct string."
204-
205-
}
206-
207-
}
208-
209-
else {
210-
211-
Write-Host "Failed to create test file."
212-
213-
}
214-
```
171+
```powershell
172+
# Virus test string
173+
$TEST_STRING = '$$89-barbados-dublin-damascus-notice-pulled-natural-31$$'
174+
 
175+
# File to be created
176+
$FILE_PATH = "C:\temp\virus_test_file.txt"
177+
 
178+
# Create "temp" directory if it does not exist
179+
$DIR_PATH = "C:\temp"
180+
if (!(Test-Path -Path $DIR_PATH)) {
181+
    New-Item -ItemType Directory -Path $DIR_PATH
182+
}
183+
 
184+
# Write the test string to the file without a trailing newline
185+
[IO.File]::WriteAllText($FILE_PATH, $TEST_STRING)
186+
 
187+
# Check if the file was created and contains the correct string
188+
if (Test-Path -Path $FILE_PATH) {
189+
    $content = [IO.File]::ReadAllText($FILE_PATH)
190+
    if ($content -eq $TEST_STRING) {
191+
        Write-Host "Test file created and validated successfully."
192+
    } else {
193+
        Write-Host "Test file does not contain the correct string."
194+
    }
195+
} else {
196+
    Write-Host "Failed to create test file."
197+
}
198+
```
199+
215200
216201
The alert `MDC_Test_File malware was detected (Agentless)` will appear within 24 hours in the Defender for Cloud Alerts page and in the Defender XDR portal.
217202

articles/hdinsight-aks/trino/trino-connect-to-metastore.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Add external Hive metastore database
33
description: Connecting to the HIVE metastore for Trino clusters in HDInsight on AKS
44
ms.service: hdinsight-aks
55
ms.topic: how-to
6-
ms.date: 10/19/2023
6+
ms.date: 02/21/2024
77
---
88

99
# Use external Hive metastore database
@@ -65,7 +65,7 @@ Configure authentication to external Hive metastore database specifying Azure Ke
6565
"secrets": [
6666
{
6767
"referenceName": "hms-db-pwd",
68-
"type": "secret",
68+
"type": "Secret",
6969
"keyVaultObjectName": "hms-db-pwd"
7070
} ]
7171
},
@@ -74,7 +74,7 @@ Configure authentication to external Hive metastore database specifying Azure Ke
7474
|---|---|---|
7575
|secretsProfile.keyVaultResourceId|Azure resource ID string to Azure Key Vault where secrets for Hive metastore are stored.|/subscriptions/0000000-0000-0000-0000-000000000000/resourceGroups/trino-rg/providers/Microsoft.KeyVault/vaults/trinoakv|
7676
|secretsProfile.secrets[*].referenceName|Unique reference name of the secret to use later in clusterProfile.|Secret1_ref|
77-
|secretsProfile.secrets[*].type|Type of object in Azure Key Vault, only “secret” is supported.|secret|
77+
|secretsProfile.secrets[*].type|Type of object in Azure Key Vault, only “Secret” is supported.|Secret|
7878
|secretsProfile.secrets[*].keyVaultObjectName|Name of secret object in Azure Key Vault containing actual secret value.|secret1|
7979

8080
### Catalog configuration
@@ -113,7 +113,7 @@ To configure external Hive metastore to an existing Trino cluster, add the requi
113113
"secrets": [
114114
{
115115
"referenceName": "hms-db-pwd",
116-
"type": "secret",
116+
"type": "Secret",
117117
"keyVaultObjectName": "hms-db-pwd"
118118
} ]
119119
},
@@ -208,7 +208,7 @@ Alternatively external Hive metastore database parameters can be specified in `t
208208
"secrets": [
209209
{
210210
"referenceName": "hms-db-pwd",
211-
"type": "secret",
211+
"type": "Secret",
212212
"keyVaultObjectName": "hms-db-pwd"
213213
} ]
214214
},
@@ -249,4 +249,4 @@ Alternatively external Hive metastore database parameters can be specified in `t
249249
}
250250
]
251251
}
252-
```
252+
```

articles/hdinsight/hdinsight-faq.yml

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ metadata:
88
ms.service: hdinsight
99
ms.custom: hdinsightactive
1010
ms.topic: faq
11-
ms.date: 02/06/2023
11+
ms.date: 02/21/2024
1212
title: "Azure HDInsight: Frequently asked questions"
1313
summary: |
1414
This article provides answers to some of the most common questions about how to run [Azure HDInsight](https://azure.microsoft.com/services/hdinsight/).
@@ -49,7 +49,7 @@ sections:
4949
1. Recommend setting up HDInsight clusters with a [Custom Ambari DB](./hdinsight-custom-ambari-db.md) to improve the cluster scalability.
5050
2. Use [Azure Data Lake Storage Gen2](./hdinsight-hadoop-use-data-lake-storage-gen2.md) to create HDInsight clusters to take advantage of higher bandwidth and other performance characteristics of Azure Data Lake Storage Gen2.
5151
3. Headnodes should be sufficiently large to accommodate multiple master services running on these nodes.
52-
4. Some specific workloads such as Interactive Query will also need larger Zookeeper nodes. Please consider minimum of 8 core VMs.
52+
4. Some specific workloads such as Interactive Query will also need larger Zookeeper nodes. Please consider minimum of eight core VMs.
5353
5. In the case of Hive and Spark, use [External Hive metastore](./hdinsight-use-external-metadata-stores.md).
5454
5555
- name: Individual Components
@@ -228,7 +228,7 @@ sections:
228228
229229
- [Enable Microsoft Entra Domain Services](domain-joined/apache-domain-joined-configure-using-azure-adds.md#enable-azure-ad-ds)
230230
231-
- [Tutorial: Configure secure LDAP for an Microsoft Entra Domain Services managed domain](../active-directory-domain-services/tutorial-configure-ldaps.md)
231+
- [Tutorial: Configure secure LDAP for Microsoft Entra Domain Services managed domain](../active-directory-domain-services/tutorial-configure-ldaps.md)
232232
233233
- question: |
234234
Can I install Data Analytics Studio (DAS) as an ESP cluster?
@@ -370,6 +370,7 @@ sections:
370370
If you call the Curl command in the same virtual network or a peered virtual network, the command is:
371371
372372
```curl
373+
373374
curl -u <cluster login username> -sS -G
374375
http://<headnodehost>:8080/api/v1/clusters/<ClusterName>/services/YARN/components/NODEMANAGER?fields=metrics/cpu
375376
```
@@ -379,19 +380,21 @@ sections:
379380
- For a non-ESP cluster:
380381
381382
```curl
383+
382384
curl -u <cluster login username> -sS -G
383385
https://<ClusterName>.azurehdinsight.net/api/v1/clusters/<ClusterName>/services/YARN/components/NODEMANAGER?fields=metrics/cpu
384386
```
385387
386388
- For an ESP cluster:
387389
388390
```curl
391+
389392
curl -u <cluster login username>-sS -G
390393
https://<ClusterName>.azurehdinsight.net/api/v1/clusters/<ClusterName>/services/YARN/components/NODEMANAGER?fields=metrics/cpu
391394
```
392395
393396
> [!NOTE]
394-
> Curl will prompt you for a password. You must enter a valid password for the cluster login username.
397+
> Curl prompts you for a password. You must enter a valid password for the cluster login username.
395398
396399
- name: Billing
397400
questions:

0 commit comments

Comments
 (0)