Skip to content

Commit 762a9e7

Browse files
committed
fix broken link
1 parent 4758a31 commit 762a9e7

File tree

3 files changed

+2
-4
lines changed

3 files changed

+2
-4
lines changed

articles/aks/howto-deploy-java-liberty-app.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -39,7 +39,7 @@ This article is intended to help you quickly get to deployment. Before going to
3939
* Install [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
4040
* Install [Docker](https://docs.docker.com/get-docker/) for your OS.
4141
* Ensure [Git](https://git-scm.com) is installed.
42-
* Make sure you're assigned either the `Owner` role or the `Contributor` and `User Access Administrator` roles in the subscription. You can verify it by following steps in [List role assignments for a user or group](../role-based-access-control/role-assignments-list-portal.md#list-role-assignments-for-a-user-or-group).
42+
* Make sure you're assigned either the `Owner` role or the `Contributor` and `User Access Administrator` roles in the subscription. You can verify it by following steps in [List role assignments for a user or group](../role-based-access-control/role-assignments-list-portal.yml).
4343

4444
> [!NOTE]
4545
> You can also execute this guidance from the [Azure Cloud Shell](/azure/cloud-shell/quickstart). This approach has all the prerequisite tools pre-installed, with the exception of Docker.

articles/azure-arc/choose-service.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -130,7 +130,7 @@ Azure Arc-enabled System Center Virtual Machine Manager also allows you to manag
130130
The following table provides a quick way to see the major capabilities of the three Azure Arc services that connect your existing Windows and Linux machines to Azure Arc.
131131

132132
| |Arc-enabled servers |Arc-enabled VMware vSphere |Arc-enabled SCVMM |Arc-enabled Azure Stack HCI |SQL Server enabled by Azure Arc |
133-
|---------|---------|---------|---------|---------|
133+
|---------|---------|---------|---------|---------|---------|
134134
|Microsoft Defender for Cloud ||||||
135135
|Microsoft Sentinel ||||||
136136
|Azure Automation ||||||

articles/defender-for-cloud/container-image-mapping.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ When a vulnerability is identified in a container image stored in a container re
1818

1919
- For Azure DevOps, [Microsoft Security DevOps (MSDO) Extension](azure-devops-extension.yml) installed on the Azure DevOps organization.
2020

21-
- For Azure DevOps, [Microsoft Security DevOps (MSDO) Extension](azure-devops-extension.md) installed on the Azure DevOps organization.
22-
2321
- For GitHub, [Microsoft Security DevOps (MSDO) Action](github-action.md) configured in your GitHub repositories. Additionally, the GitHub Workflow must have "**id-token: write"** permissions for federation with Defender for Cloud. For an example, see [this YAML](https://github.com/microsoft/security-devops-action/blob/7e3060ae1e6a9347dd7de6b28195099f39852fe2/.github/workflows/on-push-verification.yml).
2422
- [Defender CSPM](tutorial-enable-cspm-plan.md) enabled.
2523
- The container images must be built using [Docker](https://www.docker.com/) and the Docker client must be able to access the Docker server during the build.

0 commit comments

Comments
 (0)