You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-cloud/integration-defender-for-endpoint.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,7 +163,7 @@ You'll deploy Defender for Endpoint to your Linux machines in one of these ways,
163
163
- Enable for multiple subscriptions with a PowerShell script
164
164
165
165
> [!NOTE]
166
-
> When you enable automatic deployment, Defender for Endpoint for Linux installation will abort on machines with pre-existing security solutions using [fanotify](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux#system-requirements).
166
+
> When you enable automatic deployment, Defender for Endpoint for Linux installation will abort on machines with pre-existing running services using [fanotify](/microsoft-365/security/defender-endpoint/microsoft-defender-endpoint-linux#system-requirements) and other services that can also cause MDE to malfunction or may be affected by MDE, such as security services.
167
167
> After you validate potential compatibility issues, we recommend that you manually install Defender for Endpoint on these servers.
168
168
169
169
##### Existing users with Defender for Cloud's enhanced security features enabled and Microsoft Defender for Endpoint for Windows
Copy file name to clipboardExpand all lines: articles/sap/automation/plan-deployment.md
+26-24Lines changed: 26 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -224,7 +224,7 @@ The following table shows the required permissions for the service principals:
224
224
> | Azure CLI | Installing [Azure CLI](/cli/azure/install-azure-cli-linux) | Setup of Deployer and during deployments | The firewall requirements for Azure CLI installation are defined here: [Installing Azure CLI](/cli/azure/azure-cli-endpoints) |
225
225
> | PIP | 'bootstrap.pypa.io' | Setup of Deployer | See [Installing Ansible](https://docs.ansible.com/ansible/latest/installation_guide/intro_installation.html) |
> | PowerShell Gallery | 'onegetcdn.azureedge.net', 'psg-prod-centralus.azureedge.net', 'psg-prod-eastus.azureedge.net' | Setup of Windows based systems | See [PowerShell Gallery](/powershell/scripting/gallery/getting-started?#network-access-to-the-powershell-gallery) |
227
+
> | PowerShell Gallery | 'onegetcdn.azureedge.net', 'psg-prod-centralus.azureedge.net', 'psg-prod-eastus.azureedge.net' | Setup of Windows based systems | See [PowerShell Gallery](/powershell/gallery/gallery/getting-started#network-access-to-the-powershell-gallery) |
228
228
> | Windows components | 'download.visualstudio.microsoft.com', 'download.visualstudio.microsoft.com', 'download.visualstudio.com' | Setup of Windows based systems | See [Visual Studio components](/visualstudio/install/install-and-use-visual-studio-behind-a-firewall-or-proxy-server#install-visual-studio) |
229
229
> | SAP Downloads | 'softwaredownloads.sap.com' | SAP Software download | See [SAP Downloads](https://launchpad.support.sap.com/#/softwarecenter) |
@@ -302,34 +302,36 @@ The automation framework also supports having the deployment environment and SAP
302
302
303
303
The deployment environment provides the following services:
304
304
305
-
- A deployment VM, which does Terraform deployments and Ansible configuration.
305
+
- One or more deployment virtual machines, which perform the infrastructure deployments using Terraform and performs the system configuration and SAP installation using Ansible playbooks.
306
306
- A key vault, which contains service principal identity information for use by Terraform deployments.
307
307
- An Azure Firewall component, which provides outbound internet connectivity.
308
308
309
309
The deployment configuration file defines the region, environment name, and virtual network information. For example:
310
310
311
-
```json
312
-
{
313
-
"infrastructure": {
314
-
"environment": "MGMT",
315
-
"region": "westeurope",
316
-
"vnets": {
317
-
"management": {
318
-
"address_space": "0.0.0.0/25",
319
-
"subnet_mgmt": {
320
-
"prefix": "0.0.0.0/28"
321
-
},
322
-
"subnet_fw": {
323
-
"prefix": "0.0.0.0/26"
324
-
}
325
-
}
326
-
}
327
-
},
328
-
"options": {
329
-
"enable_deployer_public_ip": true
330
-
},
331
-
"firewall_deployment": true
332
-
}
311
+
```terraform
312
+
# The environment value is a mandatory field, it is used for partitioning the environments, for example (PROD and NP)
313
+
environment = "MGMT"
314
+
315
+
# The location/region value is a mandatory field, it is used to control where the resources are deployed
316
+
location = "westeurope"
317
+
318
+
# management_network_address_space is the address space for management virtual network
# management_bastion_subnet_address_prefix is a mandatory parameter if bastion is deployed and if the subnets are not defined in the workload or if existing subnets are not used
0 commit comments