Skip to content

Commit 84aa8e1

Browse files
authored
Merge pull request #110123 from v-nagta/securityandidentity
removing block from Azure Government Security + Identity
2 parents c74d8a7 + 2ebbb80 commit 84aa8e1

File tree

1 file changed

+1
-7
lines changed

1 file changed

+1
-7
lines changed

articles/azure-government/documentation-government-services-securityandidentity.md

Lines changed: 1 addition & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,6 @@ manager: pathuff
99

1010
ms.assetid: e2fe7983-5870-43e9-ae01-2d45d3102c8a
1111
ms.service: azure-government
12-
ms.devlang: na
1312
ms.topic: article
1413
ms.tgt_pltfrm: na
1514
ms.workload: azure-government
@@ -34,7 +33,6 @@ The Qualys Vulnerability Assessment agent is not available.
3433
> [!NOTE]
3534
> 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.
3635
37-
3836
### Threat detection
3937

4038
- **Specific detections**
@@ -164,10 +162,6 @@ The following features have known limitations in Azure Government:
164162
- Office 365 Groups are not supported for B2B users and can't be enabled.
165163
- 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.
166164

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-
171165
- Limitations with Multi-factor Authentication:
172166
- Hardware OATH tokens are not available in Azure Government.
173167
- 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
191185

192186
## Next steps
193187

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

Comments
 (0)