Skip to content

Commit 4cefceb

Browse files
committed
Fix conflicts
1 parent c31b413 commit 4cefceb

8 files changed

+1
-511
lines changed

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

Lines changed: 0 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -46,16 +46,13 @@ This article is intended to help you quickly get to deployment. Before going to
4646
>
4747
> :::image type="icon" source="~/reusable-content/ce-skilling/azure/media/cloud-shell/launch-cloud-shell-button.png" alt-text="Button to launch the Azure Cloud Shell." border="false" link="https://shell.azure.com":::
4848
49-
<<<<<<< HEAD
5049
* If running the commands in this guide locally (instead of Azure Cloud Shell):
5150
* Prepare a local machine with Unix-like operating system installed (for example, Ubuntu, Azure Linux, macOS, Windows Subsystem for Linux).
5251
* Install a Java SE implementation, version 17 or later. (for example, [Eclipse Open J9](https://www.eclipse.org/openj9/)).
5352
* Install [Maven](https://maven.apache.org/download.cgi) 3.5.0 or higher.
5453
* Install [Docker](https://docs.docker.com/get-docker/) for your OS.
5554
* 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#list-role-assignments-for-a-user-or-group).
5655

57-
=======
58-
>>>>>>> 7e93f91ba8d1bfe6ba30f41f9972179785c467df
5956
## Create a Liberty on AKS deployment using the portal
6057

6158
The following steps guide you to create a Liberty runtime on AKS. After completing these steps, you have an Azure Container Registry and an Azure Kubernetes Service cluster for deploying your containerized application.

articles/api-management/how-to-configure-service-fabric-backend.md

Lines changed: 0 additions & 141 deletions
This file was deleted.

articles/defender-for-cloud/alerts-schemas.md

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -10,16 +10,9 @@ ms.date: 03/25/2024
1010

1111
# Alerts schemas
1212

13-
<<<<<<< HEAD
14-
15-
You can view these security alerts in Microsoft Defender for Cloud's pages - [overview dashboard](overview-page.md), [alerts](managing-and-responding-alerts.yml), [resource health pages](investigate-resource-health.md), or [workload protections dashboard](workload-protections-dashboard.md) - and through external tools such as:
16-
=======
1713
Defender for Cloud provides alerts that help you identify, understand, and respond to security threats. Alerts are generated when Defender for Cloud detects suspicious activity or a security-related issue in your environment. You can view these alerts in the Defender for Cloud portal, or you can export them to external tools for further analysis and response.
1814

19-
You can review security alerts from the [overview dashboard](overview-page.md), [alerts](managing-and-responding-alerts.md) page, [resource health pages](investigate-resource-health.md), or [workload protections dashboard](workload-protections-dashboard.md).
20-
21-
The following external tools can be used to consume alerts from Defender for Cloud:
22-
>>>>>>> 7e93f91ba8d1bfe6ba30f41f9972179785c467df
15+
You can view these security alerts in Microsoft Defender for Cloud's pages - [overview dashboard](overview-page.md), [alerts](managing-and-responding-alerts.yml), [resource health pages](investigate-resource-health.md), or [workload protections dashboard](workload-protections-dashboard.md) - and through external tools such as:
2316

2417
- [Microsoft Sentinel](../sentinel/index.yml) - Microsoft's cloud-native SIEM. The Sentinel Connector gets alerts from Microsoft Defender for Cloud and sends them to the [Log Analytics workspace](../azure-monitor/logs/quick-create-workspace.md) for Microsoft Sentinel.
2518
- Third-party SIEMs - Send data to [Azure Event Hubs](../event-hubs/index.yml). Then integrate your Event Hubs data with a third-party SIEM. Learn more in [Stream alerts to a SIEM, SOAR, or IT Service Management solution](export-to-siem.md).

articles/defender-for-cloud/concept-regulatory-compliance-standards.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -94,9 +94,5 @@ The following regulatory standards are available in Defender for Cloud:
9494

9595
## Related content
9696

97-
<<<<<<< HEAD
9897
- [Assign regulatory compliance standards](update-regulatory-compliance-packages.yml)
9998
- [Improve regulatory compliance](regulatory-compliance-dashboard.md)
100-
=======
101-
- [Assign regulatory compliance standards](update-regulatory-compliance-packages.md)
102-
>>>>>>> 7e93f91ba8d1bfe6ba30f41f9972179785c467df

articles/defender-for-cloud/defender-for-databases-usage.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -68,11 +68,6 @@ Defender for Cloud sends email notifications when it detects anomalous database
6868
6969
## Next step
7070

71-
<<<<<<< HEAD
7271
- [Automate responses to Defender for Cloud triggers](workflow-automation.yml)
7372
- [Stream alerts to a SIEM, SOAR, or ITSM solution](export-to-siem.md)
7473
- [Suppress alerts from Defender for Cloud](alerts-suppression-rules.md)
75-
=======
76-
> [!div class="nextstepaction"]
77-
> [Automate responses to Defender for Cloud triggers](workflow-automation.md)
78-
>>>>>>> 7e93f91ba8d1bfe6ba30f41f9972179785c467df

articles/defender-for-cloud/risk-prioritization.md

Lines changed: 0 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -103,8 +103,4 @@ The risk level is determined by a context-aware risk-prioritization engine that
103103
- [Review security recommendations](review-security-recommendations.md)
104104
- [Remediate security recommendations](implement-security-recommendations.md)
105105
- [Drive remediation with governance rules](governance-rules.md)
106-
<<<<<<< HEAD
107106
- [Automate remediation responses](workflow-automation.yml)
108-
=======
109-
- [Automate remediation responses](workflow-automation.md)
110-
>>>>>>> 7e93f91ba8d1bfe6ba30f41f9972179785c467df

0 commit comments

Comments
 (0)