Skip to content

Commit e7fca73

Browse files
authored
Merge pull request #276264 from alexbuckgit/alexbuckgit/docutune-autopr-20240524-054247-9518127-ignore-build
[BULK] - DocuTune - Fix spacing and line break issues (part 5)
2 parents 092ca8b + 622eef8 commit e7fca73

9 files changed

+103
-322
lines changed

articles/cosmos-db/resource-graph-samples.md

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,10 +11,8 @@ ms.custom: subject-resourcegraph-sample
1111
# Azure Resource Graph sample queries for Azure Cosmos DB
1212
[!INCLUDE[NoSQL, MongoDB, Cassandra, Gremlin, Table](includes/appliesto-nosql-mongodb-cassandra-gremlin-table.md)]
1313

14-
This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample
15-
queries for Azure Cosmos DB. For a complete list of Azure Resource Graph samples, see
16-
[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md)
17-
and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
14+
This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample queries for Azure Cosmos DB. For a complete list of Azure Resource Graph samples, see
15+
[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md) and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
1816

1917
## Sample queries
2018

articles/cosmos-db/troubleshoot-cmk.md

Lines changed: 12 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ In Scenario 3: Expected as the Multi-tenant App is not there or deleted.
9999

100100
**Mitigation**
101101

102-
For Scenario 1: customer needs to follow Configure your azure key vault instance section on [ setup customer managed keys documentation](./how-to-setup-customer-managed-keys.md) to retrieve the Key Vault Key Uri
102+
For Scenario 1: customer needs to follow Configure your azure key vault instance section on [setup customer managed keys documentation](./how-to-setup-customer-managed-keys.md) to retrieve the Key Vault Key Uri
103103

104104
For Scenario 2: customer need to add the missing “&FederatedClientId=<00000000-0000-0000-0000-000000000000>” into the default identity.
105105

@@ -146,8 +146,9 @@ ___________________________________
146146

147147
**Error Message**
148148

149-
``Updating KeyVaultKeyUri is not supported
150-
ActivityId: 00000000-0000-0000-0000-000000000000``
149+
```Updating KeyVaultKeyUri is not supported
150+
ActivityId: 00000000-0000-0000-0000-000000000000
151+
```
151152

152153

153154
**Status Code**
@@ -174,8 +175,10 @@ A customer is trying to update the Cosmos DB CMK account which is in revoke stat
174175

175176
**Error Message**
176177

177-
``No Update is allowed on Database Account with Customer Managed Key in Revoked Status
178-
ActivityId: 00000000-0000-0000-0000-000000000000, Microsoft.Azure.Documents.Common/2.14.0``
178+
```
179+
No Update is allowed on Database Account with Customer Managed Key in Revoked Status
180+
ActivityId: 00000000-0000-0000-0000-000000000000, Microsoft.Azure.Documents.Common/2.14.0
181+
```
179182

180183

181184
**Status Code**
@@ -417,9 +420,10 @@ ___________________________________
417420

418421
**Error Message**
419422

420-
``Continuous backup mode and multiple write locations cannot be enabled together for a global database account
421-
ActivityId: 00000000-0000-0000-0000-000000000000``
422-
423+
```
424+
Continuous backup mode and multiple write locations cannot be enabled together for a global database account
425+
ActivityId: 00000000-0000-0000-0000-000000000000
426+
```
423427

424428
**Status Code**
425429

articles/data-factory/ci-cd-github-troubleshoot-guide.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -245,13 +245,13 @@ Following section isn't valid because package.json folder isn't valid.
245245
It should have DataFactory included in customCommand like *'run build validate $(Build.Repository.LocalPath)/DataFactory/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/testResourceGroup/providers/Microsoft.DataFactory/factories/yourFactoryName'*. Make sure the generated YAML file for higher stage should have required JSON artifacts.
246246

247247

248-
### Extra left "[" displayed in published JSON file
248+
### Extra left `[` displayed in published JSON file
249249

250250
#### Issue
251-
When publishing with DevOps, there's an extra "[" displayed. The service adds one more "[" in an ARM template in DevOps automatically. You'll see an expression like "[[" in JSON file.
251+
When publishing with DevOps, there's an extra `[` displayed. The service adds one more `[` in an ARM template in DevOps automatically. You'll see an expression like `[[` in JSON file.
252252

253253
#### Cause
254-
Because [ is a reserved character for ARM templates, an extra [ is added automatically to escape "[".
254+
Because `[` is a reserved character for ARM templates, an extra `[` is added automatically to escape `[`.
255255

256256
#### Resolution
257257
This is normal behavior during the publishing process for CI/CD.

articles/databox-online/azure-stack-edge-gpu-create-virtual-machine-marketplace-image.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,7 @@ The last three flags are optional but excluding them returns a long list.
5757
Some example queries are:
5858

5959
```azurecli
60-
#Returns all images of type Windows Server
60+
#Returns all images of type "Windows Server"
6161
az vm image list --all --publisher "MicrosoftWindowsserver" --offer "WindowsServer"
6262
6363
#Returns all Windows Server 2019 Datacenter images from West US published by Microsoft

articles/databox-online/azure-stack-edge-gpu-deploy-vm-specialized-image-powershell.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -293,4 +293,3 @@ This article used only one resource group to create all the VM resource. Deletin
293293
294294
- [Prepare a generalized image from a Windows VHD to deploy VMs on Azure Stack Edge Pro GPU](azure-stack-edge-gpu-prepare-windows-vhd-generalized-image.md)
295295
- [Prepare a generalized image from an ISO to deploy VMs on Azure Stack Edge Pro GPU](azure-stack-edge-gpu-prepare-windows-generalized-image-iso.md)
296-
d

articles/ddos-protection/fundamental-best-practices.md

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -28,9 +28,7 @@ Ensuring that an application is resilient enough to handle a denial of service t
2828
Scalability is how well a system can handle increased load. Design your applications to [scale horizontally](/azure/architecture/guide/design-principles/scale-out) to meet the demand of an amplified load, specifically in the event of a DDoS attack. If your application depends on a single instance of a service, it creates a single point of failure. Provisioning multiple instances makes your system more resilient and more scalable.
2929

3030
For [Azure App Service](../app-service/overview.md), select an [App Service plan](../app-service/overview-hosting-plans.md) that offers multiple instances. For Azure Cloud Services, configure each of your roles to use [multiple instances](../cloud-services/cloud-services-choose-me.md).
31-
For [Azure Virtual Machines](../virtual-machines/index.yml), ensure that your virtual machine (VM) architecture includes more than one VM and that each VM is
32-
included in an [availability set](../virtual-machines/windows/tutorial-availability-sets.md). We recommend using [virtual machine scale sets](../virtual-machine-scale-sets/overview.md)
33-
for autoscaling capabilities.
31+
For [Azure Virtual Machines](../virtual-machines/index.yml), ensure that your virtual machine (VM) architecture includes more than one VM and that each VM is included in an [availability set](../virtual-machines/windows/tutorial-availability-sets.md). We recommend using [virtual machine scale sets](../virtual-machine-scale-sets/overview.md) for autoscaling capabilities.
3432

3533
## Defense in depth
3634

articles/dedicated-hsm/quickstart-create-hsm-powershell.md

Lines changed: 8 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,7 @@ This article describes how you can create an Azure Dedicated HSM using the
1818

1919
## Requirements
2020

21-
* If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account
22-
before you begin.
21+
* If you don't have an Azure subscription, create a [free](https://azure.microsoft.com/free/) account before you begin.
2322

2423
[!INCLUDE [azure-powershell-requirements-no-header.md](../../includes/azure-powershell-requirements-no-header.md)]
2524

@@ -33,20 +32,15 @@ before you begin.
3332
Install-Module -Name Az.DedicatedHsm
3433
```
3534

36-
* If you have multiple Azure subscriptions, choose the appropriate subscription in which the
37-
resources should be billed. Select a specific subscription using the
38-
[Set-AzContext](/powershell/module/az.accounts/set-azcontext) cmdlet.
35+
* If you have multiple Azure subscriptions, choose the appropriate subscription in which the resources should be billed. Select a specific subscription using the [Set-AzContext](/powershell/module/az.accounts/set-azcontext) cmdlet.
3936

4037
```azurepowershell-interactive
4138
Set-AzContext -SubscriptionId 00000000-0000-0000-0000-000000000000
4239
```
4340

4441
## Create a resource group
4542

46-
Create an [Azure resource group](../azure-resource-manager/management/overview.md)
47-
using the [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup)
48-
cmdlet. A resource group is a logical container in which Azure resources are deployed and managed as
49-
a group.
43+
Create an [Azure resource group](../azure-resource-manager/management/overview.md) using the [New-AzResourceGroup](/powershell/module/az.resources/new-azresourcegroup) cmdlet. A resource group is a logical container in which Azure resources are deployed and managed as a group.
5044

5145
The following example creates a resource group with the specified name and in the specified location.
5246

@@ -57,8 +51,7 @@ New-AzResourceGroup -Name myRG -Location westus
5751
## Create a dedicated HSM
5852

5953
To create a dedicated HSM, you use the
60-
[New-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/new-azdedicatedhsm) cmdlet. The following
61-
example creates a dedicated HSM in the specified subscription.
54+
[New-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/new-azdedicatedhsm) cmdlet. The following example creates a dedicated HSM in the specified subscription.
6255

6356
```azurepowershell-interactive
6457
$Params = @{
@@ -82,8 +75,7 @@ myhsm Succeeded SafeNet Luna Network HSM A790 westus
8275
## Get a dedicated HSM
8376

8477
To retrieve information about an existing dedicated HSM, you use the
85-
[Get-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/get-azdedicatedhsm) cmdlet. The following
86-
example gets the specified dedicated HSM.
78+
[Get-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/get-azdedicatedhsm) cmdlet. The following example gets the specified dedicated HSM.
8779

8880
```azurepowershell-interactive
8981
Get-AzDedicatedHsm -Name MyHSM -ResourceGroupName myRG
@@ -98,8 +90,7 @@ myhsm Succeeded SafeNet Luna Network HSM A790 westus
9890
## Update a dedicated HSM
9991

10092
To update a dedicated HSM, you use the
101-
[Update-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/update-azdedicatedhsm) cmdlet. The
102-
following example updates a dedicated HSM in the specified subscription.
93+
[Update-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/update-azdedicatedhsm) cmdlet. The following example updates a dedicated HSM in the specified subscription.
10394

10495
```azurepowershell-interactive
10596
Update-AzDedicatedHsm -Name MyHSM -ResourceGroupName myRG -Tag @{'key1' = '1'; 'key2' = 2; 'key3' = 3}
@@ -116,14 +107,12 @@ myhsm Succeeded SafeNet Luna Network HSM A790 westus
116107

117108
## Clean up resources
118109

119-
If the resources created in this article aren't needed, you can delete them by running the following
120-
examples.
110+
If the resources created in this article aren't needed, you can delete them by running the following examples.
121111

122112
### Remove a dedicated HSM
123113

124114
To remove a dedicated HSM, you use the
125-
[Remove-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/remove-azdedicatedhsm) cmdlet. The
126-
following example deletes the specified dedicated HSM.
115+
[Remove-AzDedicatedHsm](/powershell/module/az.dedicatedhsm/remove-azdedicatedhsm) cmdlet. The following example deletes the specified dedicated HSM.
127116

128117
```azurepowershell-interactive
129118
Remove-AzDedicatedHsm -Name hsm-7t2xaf -ResourceGroupName lucas-manual-test

articles/defender-for-cloud/resource-graph-samples.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -8,10 +8,7 @@ ms.custom: subject-resourcegraph-sample, devx-track-azurepowershell, devx-track-
88

99
# Azure Resource Graph sample queries for Microsoft Defender for Cloud
1010

11-
This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample
12-
queries for Microsoft Defender for Cloud. For a complete list of Azure Resource Graph samples, see
13-
[Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md)
14-
and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
11+
This page is a collection of [Azure Resource Graph](../governance/resource-graph/overview.md) sample queries for Microsoft Defender for Cloud. For a complete list of Azure Resource Graph samples, see [Resource Graph samples by Category](../governance/resource-graph/samples/samples-by-category.md) and [Resource Graph samples by Table](../governance/resource-graph/samples/samples-by-table.md).
1512

1613
## Sample queries
1714

0 commit comments

Comments
 (0)