Skip to content

Commit b1b269b

Browse files
committed
2 parents e4df632 + 58d1671 commit b1b269b

File tree

7 files changed

+16
-10
lines changed

7 files changed

+16
-10
lines changed

articles/automation/automation-runbook-types.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Azure Automation runbook types
33
description: This article describes the types of runbooks that you can use in Azure Automation and considerations for determining which type to use.
44
services: automation
55
ms.subservice: process-automation
6-
ms.date: 02/12/2024
6+
ms.date: 02/22/2024
77
ms.topic: conceptual
88
ms.custom: references_regions, devx-track-python
99
---
@@ -79,7 +79,7 @@ The following are the current limitations and known issues with PowerShell runbo
7979
**Known issues**
8080
- Runbooks taking dependency on internal file paths such as `C:\modules` might fail due to changes in service backend infrastructure. Change runbook code to ensure there are no dependencies on internal file paths and use [Get-ChildItem](/powershell/module/microsoft.powershell.management/get-childitem?view=powershell-7.3&preserve-view=true) to get the required module information.
8181
- `Get-AzStorageAccount` cmdlet might fail with an error: *The `Get-AzStorageAccount` command was found in the module `Az.Storage`, but the module could not be loaded*.
82-
- Executing child scripts using `.\child-runbook.ps1` is not supported in this preview.
82+
- Executing child scripts using `.\child-runbook.ps1` is not supported.</br>
8383
**Workaround**: Use `Start-AutomationRunbook` (internal cmdlet) or `Start-AzAutomationRunbook` (from *Az.Automation* module) to start another runbook from parent runbook.
8484
- When you use [ExchangeOnlineManagement](/powershell/exchange/exchange-online-powershell?view=exchange-ps&preserve-view=true) module version: 3.0.0 or higher, you can experience errors. To resolve the issue, ensure that you explicitly upload [PowerShellGet](/powershell/module/powershellget/) and [PackageManagement](/powershell/module/packagemanagement/) modules.
8585

articles/azure-arc/kubernetes/extensions-release.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ The most recent version of the Flux v2 extension and the two previous versions (
121121
> [!NOTE]
122122
> When a new version of the `microsoft.flux` extension is released, it may take several days for the new version to become available in all regions.
123123
124-
### 1.8.2 (February 2023)
124+
### 1.8.2 (February 2024)
125125

126126
Flux version: [Release v2.1.2](https://github.com/fluxcd/flux2/releases/tag/v2.1.2)
127127

articles/backup/backup-azure-backup-server-vmware.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -427,8 +427,10 @@ With earlier versions of MABS, parallel backups were performed only across prote
427427
428428
You can modify the number of jobs by using the registry key as shown below (not present by default, you need to add it):
429429
430-
**Key Path**: `Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelIncrementalJobs\VMware`<BR>
431-
**Key Type**: DWORD (32-bit) value.
430+
**Key Path**: `HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelIncrementalJobs`<BR>
431+
**Key Type**: DWORD (32-bit) VMware.
432+
**Data**: number
433+
The value should be the number (decimal) of virtual machines that you select for parallel backup.
432434
433435
> [!NOTE]
434436
> You can modify the number of jobs to a higher value. If you set the jobs number to 1, replication jobs run serially. To increase the number to a higher value, you must consider the VMware performance. Consider the number of resources in use and additional usage required on VMWare vSphere Server, and determine the number of delta replication jobs to run in parallel. Also, this change will affect only the newly created protection groups. For existing protection groups you must temporarily add another VM to the protection group. This should update the protection group configuration accordingly. You can remove this VM from the protection group after the procedure is completed.

articles/backup/restore-azure-backup-server-vmware.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ MABS v4 supports restoring more than one VMware VMs protected from the same vCen
9393
>[!Note]
9494
>Before you increase the number of parallel recoveries, you need to consider the VMware performance. Considering the number of resources in use and additional usage required on VMware vSphere Server, you need to determine the number of recoveries to run in parallel.
9595
>
96-
>**Key Path**: `HKLM\ Software\Microsoft\Microsoft Data Protection Manager\Configuration\ MaxParallelRecoveryJobs`
96+
>**Key Path**: `HKLM\Software\Microsoft\Microsoft Data Protection Manager\Configuration\MaxParallelRecoveryJobs`
9797
>- **32 Bit DWORD**: VMware
9898
>- **Data**: `<number>`. The value should be the number (decimal) of virtual machines that you select for parallel recovery.
9999

articles/bastion/bastion-faq.md

Lines changed: 6 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -29,9 +29,13 @@ Azure Bastion doesn't move or store customer data out of the region it's deploye
2929

3030
### <a name="vwan"></a>Does Azure Bastion support Virtual WAN?
3131

32-
Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke VNet and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different VNet via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), default 0.0.0.0/0 route must not be overwritten.
32+
Yes, you can use Azure Bastion for Virtual WAN deployments. However, deploying Azure Bastion within a Virtual WAN hub isn't supported. You can deploy Azure Bastion in a spoke VNet and use the [IP-based connection](connect-ip-address.md) feature to connect to virtual machines deployed across a different VNet via the Virtual WAN hub. If the Azure Virtual WAN hub will be integrated with Azure Firewall as a [Secured Virtual Hub](../firewall-manager/secured-virtual-hub.md), the AzureBastionSubnet must reside within a Virtual Network where the default 0.0.0.0/0 route propagation is disabled at the VNet connection level.
3333

34-
### <a name="dns"></a>Can I use Azure Bastion with Azure Private DNS Zones?
34+
### <a name="vwan"></a>Does Azure Bastion support Virtual WAN?
35+
36+
### <a name="forcedtunnel"></a>Can I use Azure Bastion if I am force-tunneling Internet traffic back to On-Premises?
37+
38+
No, if you are advertising a default route (0.0.0.0/0) over ExpressRoute or VPN, and this route is being injected in to your Virtual Networks, this will break the Azure Bastion service.
3539

3640
Azure Bastion needs to be able to communicate with certain internal endpoints to successfully connect to target resources. Therefore, you *can* use Azure Bastion with Azure Private DNS Zones as long as the zone name you select doesn't overlap with the naming of these internal endpoints. Before you deploy your Azure Bastion resource, make sure that the host virtual network isn't linked to a private DNS zone with the following exact names:
3741

articles/machine-learning/concept-fairness-ml.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ ms.topic: conceptual
99
ms.author: mesameki
1010
author: mesameki
1111
ms.reviewer: lagayhar
12-
ms.date: 08/17/2022
12+
ms.date: 02/21/2024
1313
ms.custom: responsible-ml, devx-track-python
1414
#Customer intent: As a data scientist, I want to learn about machine learning fairness and how to assess and mitigate unfairness in machine learning models.
1515
---

articles/migrate/migrate-support-matrix-hyper-v-migration.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -99,7 +99,7 @@ This table summarizes support for the replication storage account for Hyper-V VM
9999
**Setting** | **Support** | **Details**
100100
--- | --- | ---
101101
General purpose V2 storage accounts (Hot and Cool tier) | Supported | GPv2 storage accounts might incur higher transaction costs than V1 storage accounts.
102-
Premium storage | Supported | However, standard storage accounts are recommended to help optimize costs.
102+
Premium storage | Supported | However, standard storage accounts are recommended to help optimize costs. Cache storage account should be standard storage account and not premium.
103103
Region | Same region as virtual machine | Storage account should be in the same region as the virtual machine being protected.
104104
Subscription | Can be different from source virtual machines | The Storage account need not be in the same subscription as the source virtual machine(s).
105105
Azure Storage firewalls for virtual networks | Supported | If you're using firewall enabled replication storage account or target storage account, ensure you [Allow trusted Microsoft services](../storage/common/storage-network-security.md#exceptions). Also, ensure that you allow access to at least one subnet of source virtual network. **You should allow access from All networks for public endpoint connectivity.**

0 commit comments

Comments
 (0)