Skip to content

Commit 4cb3893

Browse files
authored
Merge pull request #3595 from MicrosoftDocs/main
5/21/2025 PM Publish
2 parents c48b662 + 0870348 commit 4cb3893

File tree

148 files changed

+40
-205
lines changed

Some content is hidden

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

148 files changed

+40
-205
lines changed

azps-0.10.0/Az.KeyVault/Add-AzKeyVaultKey.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,7 @@ in the Key Vault REST API documentation.
5050
Note: To import a key from your own hardware security module, you must first generate a BYOK
5151
package (a file with a .byok file name extension) by using the Azure Key Vault BYOK toolset. For
5252
more information, see
53-
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](http://go.microsoft.com/fwlink/?LinkId=522252).
53+
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](/azure/key-vault/keys/hsm-protected-keys).
5454

5555
As a best practice, back up your key after it is created or updated, by using the
5656
Backup-AzKeyVaultKey cmdlet. There is no undelete functionality, so if you accidentally delete
@@ -107,7 +107,7 @@ specifies. The imported key is an HSM-protected key.
107107

108108
To import a key from your own hardware security module, you must first generate a BYOK package (a file with a .byok file name extension) by using the Azure Key Vault BYOK toolset.
109109
For more information, see
110-
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](http://go.microsoft.com/fwlink/?LinkId=522252).
110+
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](/azure/key-vault/keys/hsm-protected-keys).
111111

112112
### Example 5: Import a software-protected key
113113
```

azps-0.10.0/Az.Storage/Set-AzStorageAccount.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -121,7 +121,7 @@ The command upgrade a Storage account with Kind "Storage" or "BlobStorage" to "S
121121
Specifies the access tier of the Storage account that this cmdlet modifies.
122122
The acceptable values for this parameter are: Hot and Cool.
123123
If you change the access tier, it may result in additional charges. For more information, see
124-
[Azure Blob Storage: Hot and cool storage tiers](http://go.microsoft.com/fwlink/?LinkId=786482).
124+
[Azure Blob Storage: Hot and cool storage tiers](https://azure.microsoft.com/pricing/details/storage/blobs/).
125125
If the Storage account has Kind as StorageV2 or BlobStorage, you can specify the *AccessTier* parameter.
126126
If the Storage account has Kind as Storage, do not specify the *AccessTier* parameter.
127127

azps-12.5.0/Az.KeyVault/Add-AzKeyVaultKey.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,7 @@ in the Key Vault REST API documentation.
137137
Note: To import a key from your own hardware security module, you must first generate a BYOK
138138
package (a file with a .byok file name extension) by using the Azure Key Vault BYOK toolset. For
139139
more information, see
140-
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](http://go.microsoft.com/fwlink/?LinkId=522252).
140+
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](/azure/key-vault/keys/hsm-protected-keys).
141141
As a best practice, back up your key after it is created or updated, by using the
142142
Backup-AzKeyVaultKey cmdlet. There is no undelete functionality, so if you accidentally delete
143143
your key or delete it and then change your mind, the key is not recoverable unless you have a
@@ -276,7 +276,7 @@ This command imports the key named ITByok from the location that the *KeyFilePat
276276
specifies. The imported key is an HSM-protected key.
277277
To import a key from your own hardware security module, you must first generate a BYOK package (a file with a .byok file name extension) by using the Azure Key Vault BYOK toolset.
278278
For more information, see
279-
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](http://go.microsoft.com/fwlink/?LinkId=522252).
279+
[How to Generate and Transfer HSM-Protected Keys for Azure Key Vault](/azure/key-vault/keys/hsm-protected-keys).
280280

281281
### Example 6: Import a software-protected key
282282
```powershell

azps-12.5.0/Az.RedisCache/New-AzRedisCache.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -380,7 +380,7 @@ Standard and Premium tiers.
380380
Configures the number of databases.
381381
This property can be configured only at cache creation.
382382
Standard and Premium tiers.
383-
For more information, see Manage Azure Redis Cache with Azure PowerShellhttp://go.microsoft.com/fwlink/?LinkId=800051 (http://go.microsoft.com/fwlink/?LinkId=800051).
383+
For more information, see [Manage Azure Redis Cache with Azure PowerShell](/azure/redis/how-to-manage-redis-cache-powershell).
384384
- preferred-data-archive-auth-method
385385
Preferred auth method to communicate to storage account used for data archive, specify SAS or ManagedIdentity, default value is SAS
386386
- preferred-data-persistence-auth-method

azps-12.5.0/Az.RedisCache/Set-AzRedisCache.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -417,7 +417,7 @@ Standard and Premium tiers.
417417
Configures the number of databases.
418418
This property can be configured only at cache creation.
419419
Standard and Premium tiers.
420-
For more information, see Manage Azure Redis Cache with Azure PowerShellhttp://go.microsoft.com/fwlink/?LinkId=800051 (http://go.microsoft.com/fwlink/?LinkId=800051).
420+
For more information, see [Manage Azure Redis Cache with Azure PowerShell](/azure/redis/how-to-manage-redis-cache-powershell).
421421
- preferred-data-archive-auth-method
422422
Preferred auth method to communicate to storage account used for data archive, specify SAS or ManagedIdentity, default value is SAS
423423
- preferred-data-persistence-auth-method

azps-12.5.0/Az.Sql/Restore-AzSqlDatabase.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -666,8 +666,6 @@ This cmdlet supports the common parameters: -Debug, -ErrorAction, -ErrorVariable
666666
667667
[Recover an Azure SQL Database from an outage](http://go.microsoft.com/fwlink/?LinkId=746882)
668668
669-
[Recover an Azure SQL Database from a user error](http://go.microsoft.com/fwlink/?LinkId=746944)
670-
671669
[Get-AzSqlDatabase](./Get-AzSqlDatabase.md)
672670
673671
[Get-AzSqlDatabaseGeoBackup](./Get-AzSqlDatabaseGeoBackup.md)

azps-12.5.0/Az.Storage/Set-AzStorageAccount.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -454,7 +454,7 @@ This command updates a storage account with Keyvault from another tenant (access
454454
Specifies the access tier of the Storage account that this cmdlet modifies.
455455
The acceptable values for this parameter are: Hot and Cool.
456456
If you change the access tier, it may result in additional charges. For more information, see
457-
[Azure Blob Storage: Hot and cool storage tiers](http://go.microsoft.com/fwlink/?LinkId=786482).
457+
[Azure Blob Storage: Hot and cool storage tiers](https://azure.microsoft.com/pricing/details/storage/blobs/).
458458
If the Storage account has Kind as StorageV2 or BlobStorage, you can specify the *AccessTier* parameter.
459459
If the Storage account has Kind as Storage, do not specify the *AccessTier* parameter.
460460

azps-14.0.0/Az.Compute/Add-AzVMSecret.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Add-AzVMSecret [-VM] <PSVirtualMachine> [[-SourceVaultId] <String>] [[-Certifica
2626
The **Add-AzVMSecret** cmdlet adds a secret to a virtual machine.
2727
This value lets you add a certificate to the virtual machine.
2828
The secret must be stored in a Key Vault.
29-
For more information about Key Vault, see [What is Azure Key Vault?](https://azure.microsoft.com/documentation/articles/key-vault-whatis/).
29+
For more information about Key Vault, see [What is Azure Key Vault?](/azure/key-vault/general/overview).
3030
For more information about the cmdlets, see [Azure Key Vault Cmdlets](/powershell/module/az.keyvault) or the [Set-AzKeyVaultSecret](/powershell/module/az.keyvault/set-azkeyvaultsecret) cmdlet.
3131

3232
> [!NOTE]

azps-14.0.0/Az.ConnectedNetwork/New-AzConnectedNetworkFunctionRoleConfigurationObject.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -223,10 +223,7 @@ Specifies the name of the administrator account.
223223
224224
**Max-length (Linux):** 64 characters
225225
226-
**Max-length (Windows):** 20 characters
227-
228-
\<li\> For root access to the Linux VM, see [Using root privileges on Linux virtual machines in Azure](https://docs.microsoft.com/azure/virtual-machines/virtual-machines-linux-use-root-privileges?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json)
229-
\<li\> For a list of built-in system users on Linux that should not be used in this field, see [Selecting User Names for Linux on Azure](https://docs.microsoft.com/azure/virtual-machines/virtual-machines-linux-usernames?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json).
226+
**Max-length (Windows):** 20 characters
230227
231228
```yaml
232229
Type: System.String
@@ -252,9 +249,7 @@ The maximum length of the binary array is 65535 bytes.
252249
253250
254251
customData is passed to the VM to be saved as a file.
255-
For more information see [Custom Data on Azure VMs](https://azure.microsoft.com/en-us/blog/custom-data-and-cloud-init-on-windows-azure/)
256-
257-
For using cloud-init for your Linux VM, see [Using cloud-init to customize a Linux VM during creation](https://docs.microsoft.com/azure/virtual-machines/virtual-machines-linux-using-cloud-init?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json).
252+
For more information see [Custom Data on Azure VMs](https://azure.microsoft.com/en-us/blog/custom-data-and-cloud-init-on-windows-azure/)
258253
259254
```yaml
260255
Type: System.String

azps-14.0.0/Az.ConnectedNetwork/New-AzConnectedNetworkFunctionUserConfigurationObject.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -70,8 +70,6 @@ The maximum length of the binary array is 65535 bytes.
7070
customData is passed to the VM to be saved as a file.
7171
For more information see [Custom Data on Azure VMs](https://azure.microsoft.com/en-us/blog/custom-data-and-cloud-init-on-windows-azure/)
7272
73-
For using cloud-init for your Linux VM, see [Using cloud-init to customize a Linux VM during creation](https://docs.microsoft.com/azure/virtual-machines/virtual-machines-linux-using-cloud-init?toc=%2fazure%2fvirtual-machines%2flinux%2ftoc.json).
74-
7573
```yaml
7674
Type: System.String
7775
Parameter Sets: (All)

0 commit comments

Comments
 (0)