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/azure-government/documentation-government-services-securityandidentity.md
+1-7Lines changed: 1 addition & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,6 @@ manager: pathuff
9
9
10
10
ms.assetid: e2fe7983-5870-43e9-ae01-2d45d3102c8a
11
11
ms.service: azure-government
12
-
ms.devlang: na
13
12
ms.topic: article
14
13
ms.tgt_pltfrm: na
15
14
ms.workload: azure-government
@@ -34,7 +33,6 @@ The Qualys Vulnerability Assessment agent is not available.
34
33
> [!NOTE]
35
34
> Security Center internal assessments *are* provided to discover security misconfigurations, based on Common Configuration Enumeration such as password policy, windows FW rules, local machine audit and security policy, and additional OS hardening settings.
36
35
37
-
38
36
### Threat detection
39
37
40
38
-**Specific detections**
@@ -164,10 +162,6 @@ The following features have known limitations in Azure Government:
164
162
- Office 365 Groups are not supported for B2B users and can't be enabled.
165
163
- Some SQL tools such as SSMS require you to set the appropriate cloud parameter. In the tool's Azure Service setup options, set the cloud parameter to Azure US Government.
166
164
167
-
- Limitations with the Azure Active Directory App Gallery:
168
-
- Pre-integrated SAML and password SSO applications from the Azure AD Application Gallery are not yet available. Instead, use a custom application to support federated single sign-on with SAML or password SSO.
169
-
- Rich provisioning connectors for featured apps are not yet available. Instead, use SCIM for automated provisioning.'
170
-
171
165
- Limitations with Multi-factor Authentication:
172
166
- Hardware OATH tokens are not available in Azure Government.
173
167
- Trusted IPs are not supported in Azure Government. Instead, use Conditional Access policies with named locations to establish when Multi-Factor Authentication should and should not be required based off the user's current IP address.
@@ -191,4 +185,4 @@ For information about EMS suite capabilities in Azure Government, see the [Enter
191
185
192
186
## Next steps
193
187
194
-
For supplemental information and updates, subscribe to the [Microsoft Azure Government Blog.](https://devblogs.microsoft.com/azuregov)
188
+
For supplemental information and updates, subscribe to the [Microsoft Azure Government Blog.](https://devblogs.microsoft.com/azuregov)
0 commit comments