mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-22 22:03:46 +00:00
Merge branch 'master' into patch-2
This commit is contained in:
Tina Burden
GitHub
@ -23,7 +23,7 @@ ms.technology: mde
|
||||
**Applies to:**
|
||||
- [Microsoft Defender for Endpoint](https://go.microsoft.com/fwlink/p/?linkid=2154037)
|
||||
|
||||
Microsoft Defender for Endpoint for US Government customers, built in the US Azure Government environment, uses the same underlying technologies as Defender for Endpoint in Azure Commercial.
|
||||
Microsoft Defender for Endpoint for US Government customers, built in the Azure US Government environment, uses the same underlying technologies as Defender for Endpoint in Azure Commercial.
|
||||
|
||||
This offering is available to GCC, GCC High, and DoD customers and is based on the same prevention, detection, investigation, and remediation as the commercial version. However, there are some differences in the availability of capabilities for this offering.
|
||||
|
||||
@ -37,8 +37,8 @@ Microsoft Defender for Endpoint for US Government customers requires one of the
|
||||
GCC | GCC High | DoD
|
||||
:---|:---|:---
|
||||
Windows 10 Enterprise E5 GCC | Windows 10 Enterprise E5 for GCC High | Windows 10 Enterprise E5 for DOD
|
||||
| | Microsoft 365 E5 for GCC High |
|
||||
| | Microsoft 365 G5 Security for GCC High |
|
||||
| | Microsoft 365 E5 for GCC High | Microsoft 365 G5 for DOD
|
||||
| | Microsoft 365 G5 Security for GCC High | Microsoft 365 G5 Security for DOD
|
||||
Microsoft Defender for Endpoint - GCC | Microsoft Defender for Endpoint for GCC High | Microsoft Defender for Endpoint for DOD
|
||||
|
||||
### Server licensing
|
||||
@ -86,8 +86,8 @@ Windows 8.1 Enterprise |  |  |  | 
|
||||
Windows 7 SP1 Enterprise |  |  | 
|
||||
Windows 7 SP1 Pro |  |  | 
|
||||
Linux |  In development |  In development |  In development
|
||||
macOS |  In development |  In development |  In development
|
||||
Linux |  Rolling out |  Rolling out |  Rolling out
|
||||
macOS |  Rolling out |  Rolling out |  Rolling out
|
||||
Android |  On engineering backlog |  On engineering backlog |  On engineering backlog
|
||||
iOS |  On engineering backlog |  On engineering backlog |  On engineering backlog
|
||||
|
||||
@ -124,6 +124,20 @@ For more information, see [Configure device proxy and Internet connectivity sett
|
||||
>
|
||||
> When filtering, look for the records labeled as "US Gov" and your specific cloud under the geography column.
|
||||
|
||||
### Service backend IP ranges
|
||||
|
||||
If your network devices don't support DNS-based rules, use IP ranges instead.
|
||||
|
||||
Defender for Endpoint for US Government customers is built in the Azure US Government environment, deployed in the following regions:
|
||||
|
||||
- AzureCloud.usgovtexas
|
||||
- AzureCloud.usgovvirginia
|
||||
|
||||
You can find the Azure IP ranges in [Azure IP Ranges and Service Tags – US Government Cloud](https://www.microsoft.com/download/details.aspx?id=57063).
|
||||
|
||||
> [!NOTE]
|
||||
> As a cloud-based solution, the IP address ranges can change. It's recommended you move to DNS-based rules.
|
||||
|
||||
<br>
|
||||
|
||||
## API
|
||||
@ -138,18 +152,18 @@ SIEM | `https://wdatp-alertexporter-us.gcc.securitycenter.windows.us` | `https:/
|
||||
<br>
|
||||
|
||||
## Feature parity with commercial
|
||||
Defender for Endpoint doesn't have complete parity with the commercial offering. While our goal is to deliver all commercial features and functionality to our US Government customers, there are some capabilities not yet available we want to highlight.
|
||||
Defender for Endpoint for US Government customers doesn't have complete parity with the commercial offering. While our goal is to deliver all commercial features and functionality to our US Government customers, there are some capabilities not yet available we want to highlight.
|
||||
|
||||
These are the known gaps as of February 2021:
|
||||
These are the known gaps as of March 2021:
|
||||
|
||||
Feature name | GCC | GCC High | DoD (PREVIEW)
|
||||
:---|:---|:---|:---
|
||||
Automated investigation and remediation: Live response |  |  | 
|
||||
Automated investigation and remediation: Response to Office 365 alerts |  On engineering backlog |  On engineering backlog |  On engineering backlog
|
||||
Email notifications |  Rolling out |  Rolling out |  Rolling out
|
||||
Email notifications |  |  | 
|
||||
Evaluation lab |  |  | 
|
||||
Management and APIs: Device health and compliance report |  |  | 
|
||||
Management and APIs: Integration with third-party products |  In development |  In development |  In development
|
||||
Management and APIs: Integration with third-party products |  Rolling out |  Rolling out |  Rolling out
|
||||
Management and APIs: Streaming API |  |  In development |  In development
|
||||
Management and APIs: Threat protection report |  |  | 
|
||||
Threat & vulnerability management |  |  | 
|
||||
|
||||
@ -43,6 +43,9 @@ When network protection blocks a connection, a notification is displayed from th
|
||||
|
||||
You can also use [audit mode](audit-windows-defender.md) to evaluate how network protection would impact your organization if it were enabled.
|
||||
|
||||
> [!NOTE]
|
||||
> If network protection is enabled and platform updates are managed, it could cause some systems to lose network connectivity if their systems aren't updated. As a result, some devices might lose network connectivity. In a managed environment, make sure that Configuration Manager auto deployment rule is updating the platform. Make sure this is fully deployed to all clients before turning on network protection.
|
||||
|
||||
## Requirements
|
||||
|
||||
Network protection requires Windows 10 Pro or Enterprise, and Microsoft Defender Antivirus real-time protection.
|
||||
|
||||
Reference in New Issue
Block a user