Skip to content

Commit 9b9fcc9

Browse files
committed
updates
1 parent e778020 commit 9b9fcc9

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ Windows Defender ATP installation on Windows VMs via Security Center and the ass
4040
### Notifications
4141

4242
- **Azure activity logs**
43-
User activity in Security Center is not logged in Azure activity logs in Microsoft Azure Government. This means that theres 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.
4444

4545
### Threat detection
4646

@@ -145,7 +145,7 @@ The following Azure Active Directory Premium P1 features are currently not avail
145145
- Group-Based Licensing
146146
- Azure Active Directory Domain Services
147147
- 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)
149149

150150
The following features have known limitations in Azure Government:
151151

@@ -161,7 +161,7 @@ The following features have known limitations in Azure Government:
161161

162162
- Limitations with Multi-factor Authentication:
163163
- 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 users 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.
165165

166166
- Limitations with Azure AD Join:
167167
- Enterprise State Roaming for Windows 10 devices is not available

0 commit comments

Comments
 (0)