Skip to content

Commit e5db4d8

Browse files
authored
Merge pull request #291575 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to main to sync with https://github.com/MicrosoftDocs/azure-docs (branch main)
2 parents c3f269d + 3d0308f commit e5db4d8

10 files changed

+26
-21
lines changed

articles/automation/automation-manage-send-joblogs-log-analytics.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -110,7 +110,7 @@ Azure Automation diagnostics create the following types of records in Azure Moni
110110
| Caller_s |Caller that initiated the operation. Possible values are either an email address or system for scheduled jobs. |
111111
| Tenant_g | GUID (globally unique identifier) that identifies the tenant for the caller. |
112112
| JobId_g |GUID that identifies the runbook job. |
113-
| ResultType |Status of the runbook job. Possible values are:<br>- New<br>- Created<br>- Started<br>- Stopped<br>- Suspended<br>- Failed<br>- Completed |
113+
| ResultType |Status of the runbook job. Possible values are:<br>- Created<br>- Started<br>- Stopped<br>- Suspended<br>- Failed<br>- Completed |
114114
| Category | Classification of the type of data. For Automation, the value is JobLogs. |
115115
| OperationName | Type of operation performed in Azure. For Automation, the value is Job. |
116116
| Resource | Name of the Automation account |

articles/backup/backup-azure-security-feature-cloud.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -130,20 +130,20 @@ Follow these steps:
130130
1. Identify the items that are in soft-deleted state.
131131

132132
```powershell
133-
$vault = Get-AzRecoveryServicesVault -ResourceGroupName "yourResourceGroupName" -Name "yourVaultName"
134-
Get-AzRecoveryServicesBackupItem -BackupManagementType AzureVM -WorkloadType AzureVM -VaultID $vault.ID | Where-Object {$_.DeleteState -eq "ToBeDeleted"}
133+
$myVault = Get-AzRecoveryServicesVault -ResourceGroupName "yourResourceGroupName" -Name "yourVaultName"
134+
Get-AzRecoveryServicesBackupItem -BackupManagementType AzureVM -WorkloadType AzureVM -VaultID $myVault.ID | Where-Object {$_.DeleteState -eq "ToBeDeleted"}
135135
136136
Name ContainerType ContainerUniqueName WorkloadType ProtectionStatus HealthStatus DeleteState
137137
---- ------------- ------------------- ------------ ---------------- ------------ -----------
138138
VM;iaasvmcontainerv2;selfhostrg;AppVM1 AzureVM iaasvmcontainerv2;selfhostrg;AppVM1 AzureVM Healthy Passed ToBeDeleted
139139
140-
$myBkpItem = Get-AzRecoveryServicesBackupItem -BackupManagementType AzureVM -WorkloadType AzureVM -VaultId $myVaultID -Name AppVM1
140+
$myBkpItem = Get-AzRecoveryServicesBackupItem -BackupManagementType AzureVM -WorkloadType AzureVM -VaultId $myVault.ID -Name AppVM1
141141
```
142142

143143
2. Reverse the deletion operation that was performed when soft-delete was enabled.
144144

145145
```powershell
146-
Undo-AzRecoveryServicesBackupItemDeletion -Item $myBKpItem -VaultId $myVaultID -Force
146+
Undo-AzRecoveryServicesBackupItemDeletion -Item $myBKpItem -VaultId $myVault.ID -Force
147147
148148
WorkloadName Operation Status StartTime EndTime JobID
149149
------------ --------- ------ --------- ------- -----
@@ -152,7 +152,7 @@ Follow these steps:
152152
3. As the soft-delete is disabled, the deletion operation immediately removes the backup data.
153153

154154
```powershell
155-
Disable-AzRecoveryServicesBackupProtection -Item $myBkpItem -RemoveRecoveryPoints -VaultId $myVaultID -Force
155+
Disable-AzRecoveryServicesBackupProtection -Item $myBkpItem -RemoveRecoveryPoints -VaultId $myVault.ID -Force
156156
157157
WorkloadName Operation Status StartTime EndTime JobID
158158
------------ --------- ------ --------- ------- -----
@@ -172,4 +172,4 @@ Follow these steps:
172172
## Next steps
173173

174174
- [Overview of security features in Azure Backup](security-overview.md)
175-
- [Frequently asked questions](soft-delete-azure-backup-faq.yml).
175+
- [Frequently asked questions](soft-delete-azure-backup-faq.yml).

articles/backup/backup-azure-troubleshoot-blob-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ This article provides troubleshooting information to address issues you encounte
7979

8080
**Error message**: The required setting PITR is disabled on storage account.
8181

82-
**Recommendation**: Enable that the point-in-restore setting on the storage account. [Learn more](../storage/blobs/point-in-time-restore-manage.md?tabs=portal#enable-and-configure-point-in-time-restore).
82+
**Recommendation**: Enable that the point-in-time restore setting on the storage account. [Learn more](../storage/blobs/point-in-time-restore-manage.md?tabs=portal#enable-and-configure-point-in-time-restore).
8383

8484
### UserErrorImmutabilityPolicyConfigured
8585

articles/backup/backup-sql-server-azure-troubleshoot.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -276,19 +276,19 @@ The total string size of files depends not only on the number of files but also
276276
```sql
277277
SELECT mf.name AS LogicalName, Physical_Name AS Location FROM sys.master_files mf
278278
               INNER JOIN sys.databases db ON db.database_id = mf.database_id
279-
               WHERE db.name = N'<Database Name>'"
279+
               WHERE db.name = N'<Database Name>'
280280
```
281281

282282
Now arrange them in the following format:
283283

284284
```json
285-
[{"path":"<Location>","logicalName":"<LogicalName>","isDir":false},{"path":"<Location>","logicalName":"<LogicalName>","isDir":false}]}
285+
[{"path":"<Location>","logicalName":"<LogicalName>","isDir":false},{"path":"<Location>","logicalName":"<LogicalName>","isDir":false}]
286286
```
287287

288288
Here's an example:
289289

290290
```json
291-
[{"path":"F:\\Data\\TestDB12.mdf","logicalName":"TestDB12","isDir":false},{"path":"F:\\Log\\TestDB12_log.ldf","logicalName":"TestDB12_log","isDir":false}]}
291+
[{"path":"F:\\Data\\TestDB12.mdf","logicalName":"TestDB12","isDir":false},{"path":"F:\\Log\\TestDB12_log.ldf","logicalName":"TestDB12_log","isDir":false}]
292292
```
293293

294294
If the string size of the content exceeds 20,000 bytes, the database files are stored differently. During recovery, you won't be able to set the target file path for restore. The files will be restored to the default SQL path provided by SQL Server.
@@ -336,7 +336,7 @@ In the preceding content, you can get the logical name of the database file by u
336336
```sql
337337
SELECT mf.name AS LogicalName FROM sys.master_files mf
338338
              INNER JOIN sys.databases db ON db.database_id = mf.database_id
339-
              WHERE db.name = N'<Database Name>'"
339+
              WHERE db.name = N'<Database Name>'
340340
```
341341

342342
This file should be placed before you trigger the restore operation.

articles/backup/backup-vault-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ A Backup vault is an entity that stores the backups and recovery points created
2424

2525
- Azure Backup automatically handles storage for the vault. Choose the storage redundancy that matches your business needs when creating the Backup vault.
2626

27-
- To learn more about storage redundancy, see these articles on [geo](../storage/common/storage-redundancy.md#geo-redundant-storage), [zonal (preview)](../storage/common/storage-redundancy.md#zone-redundant-storage), and [local](../storage/common/storage-redundancy.md#locally-redundant-storage) redundancy.
27+
- To learn more about storage redundancy, see these articles on [geo](../storage/common/storage-redundancy.md#geo-redundant-storage), [zonal](../storage/common/storage-redundancy.md#zone-redundant-storage), and [local](../storage/common/storage-redundancy.md#locally-redundant-storage) redundancy.
2828

2929
## Encryption settings in the Backup vault
3030

articles/backup/selective-disk-backup-restore.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ This is supported both for Enhanced Policy as well as Standard Policy.
2121
>[!Note]
2222
>- This is supported for both backup policies - [Enhanced policy](backup-azure-vms-enhanced-policy.md) and [Standard policy](backup-during-vm-creation.md#create-a-vm-with-backup-configured).
2323
>- The *Selective disk backup and restore in Enhanced policy* is available in all Azure regions including Public, Government, and Air-Gapped regions.
24-
>- If you use selective disk backup with *Enhanced policy* on a Linux VM, ensure that *lsblk* and *lssci* are available in your distribution so that the disks are [excluded](selective-disk-backup-restore.md#enhanced-policy).
24+
>- If you use selective disk backup with *Enhanced policy* on a Linux VM, ensure that *lsblk* and *lsscsi* are available in your distribution so that the disks are [excluded](selective-disk-backup-restore.md#enhanced-policy).
2525
2626
## Scenarios
2727

articles/business-continuity-center/business-continuity-center-overview.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,8 @@ Some of the key benefits you get with Azure Business Continuity Center include:
3131

3232
## What can I manage with ABC center?
3333

34-
Azure Business Continuity Center allows you to manage data sources protected across the solutions. You can manage these resources from different environments, such as Azure and on-premises. Learn about the [supported scenarios and limitations]().
34+
Azure Business Continuity center allows you to manage data sources protected across the solutions. You can manage these resources from different environments, such as Azure and on-premises. Learn about the [supported scenarios and limitations](business-continuity-center-support-matrix.md).
35+
3536

3637
## Get started
3738

articles/update-manager/deploy-manage-updates-using-updates-view.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ The Updates blade allows you to manage machines from an updates viewpoint. It im
2222

2323
## Classic use case
2424

25-
This option is helpful when you discover a vulnerability and want to fix it by applying a specific update on all machines on which it was pending. For example, a vulnerability is discovered in software, which can potentially expose the customer's environment to risk like remote code extension. The Central IT team discovers this threat and want to secure their enterprise's environment by applying an update *abc* that would mitigate vulnerability. Using the Updates view, they can apply the update *abc* on all the impacted machines.
25+
This option is helpful when you discover a vulnerability and want to fix it by applying a specific update on all machines on which it was pending. For example, a vulnerability is discovered in software, which can potentially expose the customer's environment to risk like remote code execution. The Central IT team discovers this threat and want to secure their enterprise's environment by applying an update *abc* that would mitigate vulnerability. Using the Updates view, they can apply the update *abc* on all the impacted machines.
2626

2727
## Summarized view
2828

@@ -68,4 +68,4 @@ You can use either the **Overview** blade or select the **Updates** blade that p
6868
* [Deploy updates now (on-demand) for single machine](deploy-updates.md)
6969
* [Schedule recurring updates](scheduled-patching.md)
7070
* [Manage update settings via Portal](manage-update-settings.md)
71-
* [Manage multiple machines using update Manager](manage-multiple-machines.md)
71+
* [Manage multiple machines using update Manager](manage-multiple-machines.md)

articles/update-manager/pre-post-events-schedule-maintenance-configuration.md

Lines changed: 7 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -86,8 +86,10 @@ In the **Event Subscription Details** section, provide an appropriate name.
8686
$EventSubscriptionName = "PreEventWebhook"
8787
8888
$PreEventWebhookEndpoint = "<Webhook URL>"
89-
90-
New-AzEventGridSystemTopicEventSubscription -ResourceGroupName $ResourceGroupForSystemTopic -SystemTopicName $SystemTopicName -EventSubscriptionName $EventSubscriptionName -Endpoint $PreEventWebhookEndpoint -IncludedEventType $IncludedEventTypes
89+
90+
$dest = New-AzEventGridWebHookEventSubscriptionDestinationObject -EndpointUrl $PreEventWebhookEndpoint
91+
92+
New-AzEventGridSystemTopicEventSubscription -ResourceGroupName $ResourceGroupForSystemTopic -SystemTopicName $SystemTopicName -EventSubscriptionName $EventSubscriptionName -Endpoint $PreEventWebhookEndpoint -IncludedEventType $IncludedEventTypes -Destination $dest
9193
9294
# Azure Function
9395
@@ -268,8 +270,10 @@ In the **Event Subscription Details** section, provide an appropriate name.
268270
$EventSubscriptionName = "PreEventWebhook"
269271
270272
$PreEventWebhookEndpoint = "<Webhook URL>"
273+
274+
$dest = New-AzEventGridWebHookEventSubscriptionDestinationObject -EndpointUrl $PreEventWebhookEndpoint
271275
272-
New-AzEventGridSystemTopicEventSubscription -ResourceGroupName $ResourceGroupForSystemTopic -SystemTopicName $SystemTopicName -EventSubscriptionName $EventSubscriptionName -Endpoint $PreEventWebhookEndpoint -IncludedEventType $IncludedEventTypes
276+
New-AzEventGridSystemTopicEventSubscription -ResourceGroupName $ResourceGroupForSystemTopic -SystemTopicName $SystemTopicName -EventSubscriptionName $EventSubscriptionName -Endpoint $PreEventWebhookEndpoint -IncludedEventType $IncludedEventTypes -Destination $dest
273277
274278
# Azure Function
275279

articles/virtual-desktop/uri-scheme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ The *ms-avd* Uniform Resource Identifier scheme for Azure Virtual Desktop is now
4646
| workspaceid | Object ID (GUID). | Specify the object ID of a valid workspace.<br /><br />To get the object ID value using PowerShell, see [Retrieve the object ID of a host pool, workspace, application group, or application](powershell-module.md#retrieve-the-object-id-of-a-host-pool-workspace-application-group-or-application). You can also use [Desktop Virtualization REST APIs](/rest/api/desktopvirtualization). |
4747
| resourceid | Object ID (GUID). | Specify the object ID of a published resource contained in the workspace. The value can be for a desktop or RemoteApp.<br /><br />To get the object ID value using PowerShell, see [Retrieve the object ID of a host pool, workspace, application group, or application](powershell-module.md#retrieve-the-object-id-of-a-host-pool-workspace-application-group-or-application). You can also use [Desktop Virtualization REST APIs](/rest/api/desktopvirtualization). |
4848
| user | User Principal Name (UPN), for example `[email protected]`. | Specify a valid user with access to specified resource. |
49-
| env *(optional)* | **avdarm** (commercial Azure)<br />**avdgov** (Azure Government) | Specify the Azure cloud where resources are located. |
49+
| env *(optional)* | **avdarm** (commercial Azure)<br />**usgov** (Azure Government) | Specify the Azure cloud where resources are located. |
5050
| version | **0** | Specify the version of the connect URI scheme to use. |
5151
| launchpartnerid *(optional)*| GUID. | Specify the partner or customer-provided ID that you can use with [Azure Virtual Desktop Diagnostics](diagnostics-log-analytics.md) to help with troubleshooting. We recommend using a GUID, which you can generate with the [New-Guid](/powershell/module/microsoft.powershell.utility/new-guid) PowerShell cmdlet. |
5252
| peeractivityid *(optional)*| GUID. | Specify the partner or customer-provided ID that you can use with [Azure Virtual Desktop Diagnostics](diagnostics-log-analytics.md) to help with troubleshooting. We recommend using a GUID, which you can generate with the [New-Guid](/powershell/module/microsoft.powershell.utility/new-guid) PowerShell cmdlet. |

0 commit comments

Comments
 (0)