Skip to content

Commit 0ee0d5e

Browse files
committed
updated more absolute links
1 parent b25d4d2 commit 0ee0d5e

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

articles/migrate/best-practices-security.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -48,7 +48,7 @@ We recommend joining the appliance machine to the domain.
4848

4949
- The Migrate appliance can be deployed on the supported version of Windows Servers either using a PowerShell installation script or OVA/VHD template.
5050

51-
- **Security baseline** - We recommend hardening the OS image of Migrate appliance using [security baselines](https://learn.microsoft.com/windows/security/operating-system-security/device-management/windows-security-configuration-framework/windows-security-baselines). Download the [security compliance toolkit](https://www.microsoft.com/en-us/download/details.aspx?id=55319) to apply security baselines on Migrate Appliance machine. Using the toolkit, administrators can compare their current GPOs with Microsoft-recommended GPO baselines or other baselines, edit them, store them in GPO backup file format, and apply them via a domain controller or inject them directly into testbed hosts to test their effects.
51+
- **Security baseline** - We recommend hardening the OS image of Migrate appliance using [security baselines](/windows/security/operating-system-security/device-management/windows-security-configuration-framework/windows-security-baselines). Download the [security compliance toolkit](https://www.microsoft.com/en-us/download/details.aspx?id=55319) to apply security baselines on Migrate Appliance machine. Using the toolkit, administrators can compare their current GPOs with Microsoft-recommended GPO baselines or other baselines, edit them, store them in GPO backup file format, and apply them via a domain controller or inject them directly into testbed hosts to test their effects.
5252

5353
## Credentials handling best practices
5454

articles/storage/elastic-san/elastic-san-troubleshoot.md

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -30,15 +30,15 @@ This article lists common issues related to Azure Elastic SAN. It also provides
3030

3131
***Unable to connect to your Elastic SAN via service endpoints***
3232

33-
- [Enable](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-public-network-access) Public Network Access on the SAN
33+
- [Enable](/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-public-network-access) Public Network Access on the SAN
3434
```powershell
3535
# Set the variable values.
3636
$RgName = "<ResourceGroupName>"
3737
$EsanName = "<ElasticSanName>"
3838
# Update the Elastic San.
3939
Update-AzElasticSan -Name $EsanName -ResourceGroupName $RgName -PublicNetworkAccess Enabled
4040
```
41-
- [Configure](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-an-azure-storage-service-endpoint) service endpoints on the volume group
41+
- [Configure](/azure/storage/elastic-san/elastic-san-networking?tabs=azure-powershell#configure-an-azure-storage-service-endpoint) service endpoints on the volume group
4242
```powershell
4343
# Define some variables
4444
$RgName = "<ResourceGroupName>"
@@ -54,7 +54,7 @@ $Vnet | Set-AzVirtualNetworkSubnetConfig -Name $SubnetName -AddressPrefix $Subne
5454

5555
- Check your SAN size and configuration via portal (SAN homepage -> Configuration blade) and ensure that the I/O per second (IOPS) and throughput numbers can handle the requirements of the workload
5656
- Check your VM throughput and IOPS limits and ensure that the VM can handle the workload requirements
57-
- Ensure that you're following the best practices outlined in this [document](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-best-practices).
57+
- Ensure that you're following the best practices outlined in this [document](/azure/storage/elastic-san/elastic-san-best-practices).
5858

5959

6060
***Unable to establish connectivity from new nodes in a cluster***
@@ -73,8 +73,8 @@ $Vnet | Set-AzVirtualNetworkSubnetConfig -Name $SubnetName -AddressPrefix $Subne
7373
- Run the script on your VM. These values can also be entered during runtime of the script.
7474

7575
## Next steps
76-
- [Deploy an Elastic SAN](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-create)
77-
- [Connect to Windows](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-windows)
78-
- [Connect to Linux](https://learn.microsoft.com/azure/storage/elastic-san/elastic-san-connect-linux)
79-
- [Connect to Azure VMware Solution](https://learn.microsoft.com/azure/azure-vmware/configure-azure-elastic-san?toc=/azure/storage/elastic-san/toc.json)
76+
- [Deploy an Elastic SAN](/azure/storage/elastic-san/elastic-san-create)
77+
- [Connect to Windows](/azure/storage/elastic-san/elastic-san-connect-windows)
78+
- [Connect to Linux](/azure/storage/elastic-san/elastic-san-connect-linux)
79+
- [Connect to Azure VMware Solution](/azure/azure-vmware/configure-azure-elastic-san?toc=/azure/storage/elastic-san/toc.json)
8080

0 commit comments

Comments
 (0)