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
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ Windows Defender ATP installation on Windows VMs via Security Center and the ass
40
40
### Notifications
41
41
42
42
-**Azure activity logs**
43
-
User activity in Security Center is not logged in Azure activity logs in Microsoft Azure Government. This means that there’s no trace or audit for user performed actions.
43
+
User activity in Security Center is not logged in Azure activity logs in Microsoft Azure Government. This means that there's no trace or audit for user performed actions.
44
44
45
45
### Threat detection
46
46
@@ -145,7 +145,7 @@ The following Azure Active Directory Premium P1 features are currently not avail
145
145
- Group-Based Licensing
146
146
- Azure Active Directory Domain Services
147
147
- Cloud App Security
148
-
- B2B Collaboration is available in Azure US Government tenants created after June, 2019. Over time, more tenants will get access to this functionality. (See [How can I tell if B2B collaboration is available in my tenant?](https://docs.microsoft.com/azure/active-directory/b2b/current-limitations#how-can-I-tell-if-b2b-collaboration-is-available-in-my-tenant)) This feature is not available in other Azure Government tenants ([vote for this feature](https://feedback.azure.com/forums/558487-azure-government/suggestions/20588554-azure-ad-b2b-in-azure-government)).
148
+
- B2B Collaboration is available in Azure US Government tenants created after June, 2019. Over time, more tenants will get access to this functionality. See [How can I tell if B2B collaboration is available in my Azure US Government tenant?](../active-directory/b2b/current-limitations.md#how-can-i-tell-if-b2b-collaboration-is-available-in-my-azure-us-government-tenant)
149
149
150
150
The following features have known limitations in Azure Government:
151
151
@@ -161,7 +161,7 @@ The following features have known limitations in Azure Government:
161
161
162
162
- Limitations with Multi-factor Authentication:
163
163
- Hardware OATH tokens are not available in Azure Government.
164
-
- 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.
164
+
- 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.
165
165
166
166
- Limitations with Azure AD Join:
167
167
- Enterprise State Roaming for Windows 10 devices is not available
0 commit comments