Skip to content

Commit 318fddf

Browse files
Merge pull request #271544 from v-savila/update-absolute-links
Bulk update: Global effort to fix validation errors
2 parents cff0df4 + 1e3d10c commit 318fddf

File tree

5 files changed

+10
-12
lines changed

5 files changed

+10
-12
lines changed

articles/mysql/flexible-server/release-notes/april-2024.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ All existing engine version server upgrades to 8.0.36 engine version.
1919
To check your engine version, run `SELECT VERSION();` command at the MySQL prompt
2020

2121
## Features
22-
### [Microsoft Defender for Cloud](https://learn.microsoft.com/azure/defender-for-cloud/defender-for-databases-introduction)
22+
### [Microsoft Defender for Cloud](/azure/defender-for-cloud/defender-for-databases-introduction)
2323
- Introducing Defender for Cloud support to simplify security management with threat protection from anomalous database activities in Azure Database for MySQL flexible server instances.
2424

2525
## Improvement

articles/mysql/flexible-server/whats-new.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This article summarizes new releases and features in Azure Database for MySQL fl
2727
## April 2024
2828
- **Microsoft Defender for Cloud supports Azure Database for MySQL flexible server (General Availability)**
2929

30-
We’re excited to announce the general availability of the Microsoft Defender for Cloud feature for Azure Database for MySQL flexible server in all service tiers. The Microsoft Defender Advanced Threat Protection feature simplifies security management of Azure Database for MySQL flexible server instances. It monitors the server for anomalous or suspicious databases activities to detect potential threats and provides security alerts for you to investigate and take appropriate action, allowing you to actively improve the security posture of your database without being a security expert. [Learn more](https://learn.microsoft.com/azure/defender-for-cloud/defender-for-databases-introduction)
30+
We’re excited to announce the general availability of the Microsoft Defender for Cloud feature for Azure Database for MySQL flexible server in all service tiers. The Microsoft Defender Advanced Threat Protection feature simplifies security management of Azure Database for MySQL flexible server instances. It monitors the server for anomalous or suspicious databases activities to detect potential threats and provides security alerts for you to investigate and take appropriate action, allowing you to actively improve the security posture of your database without being a security expert. [Learn more](/azure/defender-for-cloud/defender-for-databases-introduction)
3131
- **Known Issues**
3232

3333
While attempting to enable the Microsoft Defender for Cloud feature for an Azure Database for MySQL flexible server, you may encounter the following error: ‘The server <server_name> is not compatible with Advanced Threat Protection. Please contact Microsoft support to update the server to a supported version.’ This issue can occur on MySQL Flexible Servers that are still awaiting an internal update. It will be automatically resolved in the next internal update of your server. Alternatively, you can open a support ticket to expedite an immediate update.”

articles/trusted-signing/how-to-sign-ci-policy.md

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -17,8 +17,8 @@ To sign new CI policies with the service first install several prerequisites.
1717
Prerequisites:
1818
* A Trusted Signing account, Identity Validation, and Certificate Profile.
1919
* Ensure there are proper individual or group role assignments for signing (“Trusted Signing Certificate Profile Signer” role).
20-
* [Azure PowerShell on Windows](https://learn.microsoft.com/powershell/azure/install-azps-windows) installed
21-
* [Az.CodeSigning](https://learn.microsoft.com/powershell/module/az.codesigning/) module downloaded
20+
* [Azure PowerShell on Windows](/powershell/azure/install-azps-windows) installed
21+
* [Az.CodeSigning](/powershell/module/az.codesigning/) module downloaded
2222

2323
Overview of steps:
2424
1. ⁠Unzip the Az.CodeSigning module to a folder
@@ -33,8 +33,7 @@ Import-Module .\Az.CodeSigning.psd1
3333
"TrustedSigningAccountName": "<Trusted Signing Account Name>",
3434
"CertificateProfileName": "<Certificate Profile Name>",
3535
```
36-
37-
5. [Get the root certificate](https://learn.microsoft.com/powershell/module/az.codesigning/get-azcodesigningrootcert) to be added to the trust store
36+
5. [Get the root certificate](/powershell/module/az.codesigning/get-azcodesigningrootcert) to be added to the trust store
3837
```
3938
Get-AzCodeSigningRootCert -AccountName TestAccount -ProfileName TestCertProfile -EndpointUrl https://xxx.codesigning.azure.net/ -Destination c:\temp\root.cer
4039
```
@@ -65,6 +64,5 @@ Invoke-AzCodeSigningCIPolicySigning -MetadataFilePath C:\temp\metadata.json -Pat
6564
## Creating and Deploying a CI Policy
6665

6766
For steps on creating and deploying your CI policy refer to:
68-
* [Use signed policies to protect Windows Defender Application Control against tampering](https://learn.microsoft.com/windows/security/application-security/application-control/windows-defender-application-control/deployment/use-signed-policies-to-protect-wdac-against-tampering)
69-
* [Windows Defender Application Control design guide](https://learn.microsoft.com/windows/security/application-security/application-control/windows-defender-application-control/design/wdac-design-guide)
70-
67+
* [Use signed policies to protect Windows Defender Application Control against tampering](/windows/security/application-security/application-control/windows-defender-application-control/deployment/use-signed-policies-to-protect-wdac-against-tampering)
68+
* [Windows Defender Application Control design guide](/windows/security/application-security/application-control/windows-defender-application-control/design/wdac-design-guide)

articles/trusted-signing/how-to-signing-integrations.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,6 +120,6 @@ This section explains how to set up other not [SignTool](#set-up-signtool-with-t
120120

121121
* PowerShell for Authenticode – To use PowerShell for Trusted Signing, visit [PowerShell Gallery | Trusted Signing 0.3.8](https://www.powershellgallery.com/packages/TrustedSigning/0.3.8) to install the PowerShell module.
122122

123-
* Azure PowerShell: App Control for Business CI Policy – To use Trusted Signing for CI policy signing follow the instructions at [Signing a New CI policy](./how-to-sign-ci-policy.md) and visit the [Az.CodeSigning PowerShell Module](https://learn.microsoft.com/powershell/azure/install-azps-windows).
123+
* Azure PowerShell: App Control for Business CI Policy – To use Trusted Signing for CI policy signing follow the instructions at [Signing a New CI policy](./how-to-sign-ci-policy.md) and visit the [Az.CodeSigning PowerShell Module](/powershell/azure/install-azps-windows).
124124

125-
* Trusted Signing SDK – To create your own signing integration our [Trusted Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk) is publicly available.
125+
* Trusted Signing SDK – To create your own signing integration our [Trusted Signing SDK](https://www.nuget.org/packages/Azure.CodeSigning.Sdk) is publicly available.

articles/trusted-signing/tutorial-assign-roles.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Complete the following steps to assign roles in Trusted Signing.
3232
2. Select on the **Roles** tab and search "Trusted Signing". You can see in the screenshot below the two custom roles.
3333
![Screenshot of Azure portal UI with the Trusted Signing custom RBAC roles.](./media/trusted-signing-rbac-roles.png)
3434

35-
3. To assign these roles, select on the **Add** drop down and select **Add role assignment**. Follow the [Assign roles in Azure](https://docs.microsoft.com/azure/role-based-access-control/role-assignments-portal?tabs=current) guide to assign the relevant roles to your identities. _You'll need at least a Contributor role to create a Trusted Signing account and certificate profile._
35+
3. To assign these roles, select on the **Add** drop down and select **Add role assignment**. Follow the [Assign roles in Azure](/azure/role-based-access-control/role-assignments-portal?tabs=current) guide to assign the relevant roles to your identities. _You'll need at least a Contributor role to create a Trusted Signing account and certificate profile._
3636
4. For more granular access control on the certificate profile level, you can use the Azure CLI to assign roles. The following commands can be used to assign the _Code Signing Certificate Profile Signer_ role to users/service principles to sign files.
3737
```
3838
az role assignment create --assignee <objectId of user/service principle>

0 commit comments

Comments
 (0)