Skip to content

Commit a8a83be

Browse files
authored
Merge pull request #223558 from cmcclister/cm-linkfix-20230110-1
LinkFix: azure-docs-pr (2023-01) - 1
2 parents f5536b1 + 393f786 commit a8a83be

File tree

50 files changed

+143
-149
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

50 files changed

+143
-149
lines changed

articles/confidential-computing/quick-create-confidential-vm-azure-cli-amd.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Create a VM with the [az vm create](/cli/azure/vm) command.
4444
The following example creates a VM named *myVM* and adds a user account named *azureuser*. The `--generate-ssh-keys` parameter is used to automatically generate an SSH key, and put it in the default key location(*~/.ssh*). To use a specific set of keys instead, use the `--ssh-key-values` option.
4545
For `size`, select a confidential VM size. For more information, see [supported confidential VM families](virtual-machine-solutions-amd.md).
4646

47-
Choose `VMGuestStateOnly` for no OS disk confidential encryption. Or, choose `DiskWithVMGuestState` for OS disk confidential encryption with a platform-managed key. Enabling secure boot is optional, but recommended. For more information, see [secure boot and vTPM](/azure/virtual-machines/trusted-launch). For more information on disk encryption, see [confidential OS disk encryption](confidential-vm-overview.md).
47+
Choose `VMGuestStateOnly` for no OS disk confidential encryption. Or, choose `DiskWithVMGuestState` for OS disk confidential encryption with a platform-managed key. Enabling secure boot is optional, but recommended. For more information, see [secure boot and vTPM](../virtual-machines/trusted-launch.md). For more information on disk encryption, see [confidential OS disk encryption](confidential-vm-overview.md).
4848

4949
```azurecli-interactive
5050
az vm create \
@@ -108,7 +108,7 @@ az keyvault set-policy -n keyVaultName -g myResourceGroup --object-id $desIdenti
108108
```azurecli-interactive
109109
$diskEncryptionSetID=(az disk-encryption-set show -n diskEncryptionSetName -g myResourceGroup --query [id] -o tsv)
110110
```
111-
6. Create a VM with the [az vm create](/cli/azure/vm) command. Choose `DiskWithVMGuestState` for OS disk confidential encryption with a customer-managed key. Enabling secure boot is optional, but recommended. For more information, see [secure boot and vTPM](/azure/virtual-machines/trusted-launch). For more information on disk encryption, see [confidential OS disk encryption](confidential-vm-overview.md).
111+
6. Create a VM with the [az vm create](/cli/azure/vm) command. Choose `DiskWithVMGuestState` for OS disk confidential encryption with a customer-managed key. Enabling secure boot is optional, but recommended. For more information, see [secure boot and vTPM](../virtual-machines/trusted-launch.md). For more information on disk encryption, see [confidential OS disk encryption](confidential-vm-overview.md).
112112

113113
```azurecli-interactive
114114
az vm create \
@@ -186,4 +186,4 @@ echo -n $JWT | cut -d "." -f 2 | base64 -d 2>/dev/null | jq .
186186
## Next steps
187187

188188
> [!div class="nextstepaction"]
189-
> [Create a confidential VM on AMD with an ARM template](quick-create-confidential-vm-arm-amd.md)
189+
> [Create a confidential VM on AMD with an ARM template](quick-create-confidential-vm-arm-amd.md)

articles/cosmos-db/mongodb/how-to-python-manage-databases.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The preceding code snippet displays output similar to the following example cons
5757

5858
## Does database exist?
5959

60-
The PyMongo driver for Python creates a database if it doesn't exist when you access it. However, we recommend that instead you use the [MongoDB extension commands](/azure/cosmos-db/mongodb/custom-commands) to manage data stored in Azure Cosmos DB’s API for MongoDB. To create a new database if it doesn't exist, use the [create database extension](/azure/cosmos-db/mongodb/custom-commands#create-database) as shown in the following code snippet.
60+
The PyMongo driver for Python creates a database if it doesn't exist when you access it. However, we recommend that instead you use the [MongoDB extension commands](./custom-commands.md) to manage data stored in Azure Cosmos DB’s API for MongoDB. To create a new database if it doesn't exist, use the [create database extension](./custom-commands.md#create-database) as shown in the following code snippet.
6161

6262
To see if the database already exists before using it, get the list of current databases with the [list_database_names](https://pymongo.readthedocs.io/en/stable/api/pymongo/mongo_client.html#pymongo.mongo_client.MongoClient.list_database_names) method.
6363

@@ -83,7 +83,7 @@ The preceding code snippet displays output similar to the following example cons
8383

8484
## Get database object instance
8585

86-
If a database doesn't exist, the PyMongo driver for Python creates it when you access it. However, we recommend that instead you use the [MongoDB extension commands](/azure/cosmos-db/mongodb/custom-commands) to manage data stored in Azure Cosmos DB’s API for MongoDB. The pattern is shown above in the section [Does database exist?](#does-database-exist).
86+
If a database doesn't exist, the PyMongo driver for Python creates it when you access it. However, we recommend that instead you use the [MongoDB extension commands](./custom-commands.md) to manage data stored in Azure Cosmos DB’s API for MongoDB. The pattern is shown above in the section [Does database exist?](#does-database-exist).
8787

8888
When working with PyMongo, you access databases using attribute style access on MongoClient instances. Once you have a database instance, you can use database level operations as shown below.
8989

@@ -106,4 +106,4 @@ The preceding code snippet displays output similar to the following example cons
106106

107107
## See also
108108

109-
- [Get started with Azure Cosmos DB for MongoDB and Python](how-to-python-get-started.md)
109+
- [Get started with Azure Cosmos DB for MongoDB and Python](how-to-python-get-started.md)

articles/cosmos-db/nosql/how-to-python-get-started.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -351,7 +351,7 @@ In your *app.py*:
351351
:::code language="python" source="~/cosmos-db-nosql-python-samples/003-how-to/app_aad_default.py" id="credential":::
352352

353353
> [!IMPORTANT]
354-
> For details on how to add the correct role to enable `DefaultAzureCredential` to work, see [Configure role-based access control with Azure Active Directory for your Azure Cosmos DB account](/azure/cosmos-db/how-to-setup-rbac). In particular, see the section on creating roles and assigning them to a principal ID.
354+
> For details on how to add the correct role to enable `DefaultAzureCredential` to work, see [Configure role-based access control with Azure Active Directory for your Azure Cosmos DB account](../how-to-setup-rbac.md). In particular, see the section on creating roles and assigning them to a principal ID.
355355
356356
#### Create CosmosClient with a custom credential implementation
357357

@@ -401,7 +401,7 @@ The following guides show you how to use each of these classes to build your app
401401
|--|---|
402402
| [Create a database](how-to-python-create-database.md) | Create databases |
403403
| [Create container](how-to-python-create-container.md) | Create containers |
404-
| [Item examples](/azure/cosmos-db/nosql/samples-python#item-examples) | Point read a specific item |
404+
| [Item examples](./samples-python.md#item-examples) | Point read a specific item |
405405

406406
## See also
407407

@@ -416,4 +416,4 @@ The following guides show you how to use each of these classes to build your app
416416
Now that you've connected to an API for NoSQL account, use the next guide to create and manage databases.
417417

418418
> [!div class="nextstepaction"]
419-
> [Create a database in Azure Cosmos DB for NoSQL using Python](how-to-python-create-database.md)
419+
> [Create a database in Azure Cosmos DB for NoSQL using Python](how-to-python-create-database.md)

articles/cosmos-db/nosql/kafka-connector-sink.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -342,4 +342,4 @@ You can learn more about change feed in Azure Cosmo DB with the following docs:
342342
* [Reading from change feed](read-change-feed.md)
343343

344344
You can learn more about bulk operations in V4 Java SDK with the following docs:
345-
* [Perform bulk operations on Azure Cosmos DB data](/azure/cosmos-db/nosql/bulk-executor-java)
345+
* [Perform bulk operations on Azure Cosmos DB data](./bulk-executor-java.md)

articles/cosmos-db/nosql/throughput-control-spark.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.author: thvankra
1616
The [Spark Connector](quickstart-spark.md) allows you to communicate with Azure Cosmos DB using [Apache Spark](https://spark.apache.org/). This article describes how the throughput control feature works. Check out our [Spark samples in GitHub](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/cosmos/azure-cosmos-spark_3_2-12/Samples) to get started using throughput control.
1717

1818
> [!TIP]
19-
> This article documents the use of global throughput control groups in the Azure Cosmos DB Spark Connector, but the functionality is also available in the [Java SDK](/azure/cosmos-db/nosql/sdk-java-v4). In the SDK, you can also use Local Throughput Control groups to limit the RU consumption in the context of a single client connection instance. For example, you can apply this to different operations within a single microservice, or maybe to a single data loading program. Take a look at a code snippet [here](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-cosmos/src/samples/java/com/azure/cosmos/ThroughputControlCodeSnippet.java) for how to build a CosmosAsyncClient with both local and global control groups.
19+
> This article documents the use of global throughput control groups in the Azure Cosmos DB Spark Connector, but the functionality is also available in the [Java SDK](./sdk-java-v4.md). In the SDK, you can also use Local Throughput Control groups to limit the RU consumption in the context of a single client connection instance. For example, you can apply this to different operations within a single microservice, or maybe to a single data loading program. Take a look at a code snippet [here](https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/cosmos/azure-cosmos/src/samples/java/com/azure/cosmos/ThroughputControlCodeSnippet.java) for how to build a CosmosAsyncClient with both local and global control groups.
2020
2121
## Why is throughput control important?
2222

@@ -110,4 +110,4 @@ In each client record, the `loadFactor` attribute represents the load on the giv
110110

111111
* [Spark samples in GitHub](https://github.com/Azure/azure-sdk-for-java/tree/main/sdk/cosmos/azure-cosmos-spark_3_2-12/Samples).
112112
* [Manage data with Azure Cosmos DB Spark 3 OLTP Connector for API for NoSQL](quickstart-spark.md).
113-
* Learn more about [Apache Spark](https://spark.apache.org/).
113+
* Learn more about [Apache Spark](https://spark.apache.org/).

articles/defender-for-cloud/alerts-suppression-rules.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ Some examples of how to use suppression rule are:
3636

3737
You can apply suppression rules to management groups or to subscriptions.
3838

39-
- To suppress alerts for a management group, use [Azure Policy](/azure/governance/policy/overview).
39+
- To suppress alerts for a management group, use [Azure Policy](../governance/policy/overview.md).
4040
- To suppress alerts for subscriptions, use the Azure portal or the [REST API](#create-and-manage-suppression-rules-with-the-api).
4141

4242
Alert types that were never triggered on a subscription or management group before the rule was created won't be suppressed.
@@ -101,4 +101,4 @@ This article described the suppression rules in Microsoft Defender for Cloud tha
101101

102102
Learn more about security alerts:
103103

104-
- [Security alerts generated by Defender for Cloud](alerts-reference.md)
104+
- [Security alerts generated by Defender for Cloud](alerts-reference.md)

articles/defender-for-cloud/defender-for-containers-vulnerability-assessment-azure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -177,8 +177,8 @@ Some images may reuse tags from an image that was already scanned. For example,
177177

178178
Currently, Defender for Containers can scan images in Azure Container Registry (ACR) and AWS Elastic Container Registry (ECR) only.
179179
Docker Registry, Microsoft Artifact Registry/Microsoft Container Registry, and Microsoft Azure Red Hat OpenShift (ARO) built-in container image registry aren't supported.
180-
Images should first be imported to ACR. Learn more about [importing container images to an Azure container registry](/azure/container-registry/container-registry-import-images?tabs=azure-cli).
180+
Images should first be imported to ACR. Learn more about [importing container images to an Azure container registry](../container-registry/container-registry-import-images.md?tabs=azure-cli).
181181

182182
## Next steps
183183

184-
Learn more about the [advanced protection plans of Microsoft Defender for Cloud](enhanced-security-features-overview.md).
184+
Learn more about the [advanced protection plans of Microsoft Defender for Cloud](enhanced-security-features-overview.md).

articles/defender-for-cloud/defender-for-sql-introduction.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ When you enable **Microsoft Defender for Azure SQL**, all supported resources th
3030

3131
A vulnerability assessment service discovers, tracks, and helps you remediate potential database vulnerabilities. Assessment scans provide an overview of your SQL machines' security state, and details of any security findings. Defender for Azure SQL helps you identify and mitigate potential database vulnerabilities and detecting anomalous activities that could indicate threats to your databases.
3232

33-
Learn more about [vulnerability assessment for Azure SQL Database](/azure/defender-for-cloud/sql-azure-vulnerability-assessment-overview).
33+
Learn more about [vulnerability assessment for Azure SQL Database](./sql-azure-vulnerability-assessment-overview.md).
3434

3535
### Advanced threat protection
3636

@@ -50,4 +50,4 @@ In this article, you learned about Microsoft Defender for Azure SQL. Now you can
5050

5151
- [Enable Microsoft Defender for Azure SQL](quickstart-enable-database-protections.md)
5252
- [How Microsoft Defender for Azure SQL can protect SQL servers anywhere](https://www.youtube.com/watch?v=V7RdB6RSVpc).
53-
- [Set up email notifications for security alerts](configure-email-notifications.md)
53+
- [Set up email notifications for security alerts](configure-email-notifications.md)

articles/defender-for-cloud/defender-for-sql-on-machines-vulnerability-assessment.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ ms.date: 11/09/2021
1616
- [SQL Server on Azure Arc-enabled servers](/sql/sql-server/azure-arc/overview)
1717
- [SQL Server running on Windows machines without Azure Arc](../azure-monitor/agents/agent-windows.md)
1818

19-
The integrated [vulnerability assessment scanner](/azure/defender-for-cloud/sql-azure-vulnerability-assessment-overview) discovers, tracks, and helps you remediate potential database vulnerabilities. Assessment scans findings provide an overview of your SQL machines' security state, and details of any security findings.
19+
The integrated [vulnerability assessment scanner](./sql-azure-vulnerability-assessment-overview.md) discovers, tracks, and helps you remediate potential database vulnerabilities. Assessment scans findings provide an overview of your SQL machines' security state, and details of any security findings.
2020

2121
> [!NOTE]
2222
> The scan is lightweight, safe, only takes a few seconds per database to run and is entirely read-only. It does not make any changes to your database.
@@ -143,4 +143,4 @@ You can specify the region where your SQL Vulnerability Assessment data will be
143143

144144
## Next steps
145145

146-
Learn more about Defender for Cloud's protections for SQL resources in [Overview of Microsoft Defender for SQL](defender-for-sql-introduction.md).
146+
Learn more about Defender for Cloud's protections for SQL resources in [Overview of Microsoft Defender for SQL](defender-for-sql-introduction.md).

articles/defender-for-cloud/episode-eighteen.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,7 +29,7 @@ ms.date: 11/03/2022
2929

3030
## Recommended resources
3131

32-
Learn more about [Enable Microsoft Defender for Azure Cosmos DB](/azure/defender-for-cloud/defender-for-databases-enable-cosmos-protections)
32+
Learn more about [Enable Microsoft Defender for Azure Cosmos DB](./defender-for-databases-enable-cosmos-protections.md)
3333

3434
- Subscribe to [Microsoft Security on YouTube](https://www.youtube.com/redirect?event=video_description&redir_token=QUFFLUhqa0ZoTml2Qm9kZ2pjRzNMUXFqVUwyNl80YVNtd3xBQ3Jtc0trVm9QM2Z0NlpOeC1KSUE2UEd1cVJ5aHQ0MTN6WjJEYmNlOG9rWC1KZ1ZqaTNmcHdOOHMtWXRLSGhUTVBhQlhhYzlUc2xmTHZtaUpkd1c4LUQzLWt1YmRTbkVQVE5EcTJIM0Foc042SGdQZU5acVRJbw&q=https%3A%2F%2Faka.ms%2FSubscribeMicrosoftSecurity)
3535

@@ -45,4 +45,4 @@ Learn more about [Enable Microsoft Defender for Azure Cosmos DB](/azure/defender
4545
## Next steps
4646

4747
> [!div class="nextstepaction"]
48-
> [Defender for DevOps | Defender for Cloud in the field](episode-nineteen.md)
48+
> [Defender for DevOps | Defender for Cloud in the field](episode-nineteen.md)

0 commit comments

Comments
 (0)