Skip to content

Commit f5df35f

Browse files
committed
Acrolinx edit
1 parent 0e8c414 commit f5df35f

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

articles/active-directory/user-help/user-help-auth-app-android-china.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,21 +23,24 @@ The Microsoft Authenticator app for Android is available for download in China.
2323
- [Huawei](https://appgallery.cloud.huawei.com/uowap/index.html#/detailApp/C100262999?source=appshare&subsource=C100262999&shareTo=weixin&locale=zh_CN)
2424
- [Samsung Galaxy Store](http://apps.samsung.com/appquery/appDetail.as?appId=com.azure.authenticator)
2525

26-
The most current build of the app is in the Google Play Store, but we're making best efforts to update the app on all other app stores. Because there is no custom Android application package (APK) deployed to any app store, the app can be seamlessly updated either from the store it was downloaded from or the Google Play Store if the user crosses regions.
26+
The most current build of the app is in the Google Play Store, but we're updating the app on all other app stores as quickly as we can. Because there's no custom Android application package (APK) deployed to any app store, the app can be seamlessly updated from one of the following locations:
27+
28+
- The store it was downloaded from
29+
- The Google Play Store if the user crosses regions
2730

2831
## Limitations
2932

3033
The Microsoft Authenticator app for Android uses Google’s Firebase Cloud Messaging system and Google Play Services to receive push notifications. Because neither service is available in China, there are some limitations in functionalities of the app:
3134

32-
- Registration of the Authenticator app as a multi-factor authentication authentication method using push notifications will not work.
35+
- Registration of the Authenticator app as a multi-factor authentication (MFA) method using push notifications doesn't work.
3336

34-
- [Phone sign-in](https://docs.microsoft.com/en-us/azure/active-directory/user-help/howto-authentication-sms-signin) can't be set up because it requires the user to set up the app as an multi-factor authentication method capable of receiving push notifications, which currently don't work.
37+
- [Phone sign-in](https://docs.microsoft.com/en-us/azure/active-directory/user-help/howto-authentication-sms-signin) can't be set up. It requires the user to set up the app as an MFA method using push notifications, which currently don't work.
3538

36-
If a user has previously managed to set up phone sign-in or multi-factor authentication using the app, they will be able to perform a manual check for notifications requests in the app and use it for identity verification.
39+
If a user has previously managed to set up phone sign-in or multi-factor authentication using the app, they can perform a manual check for notifications requests in the app and use it for identity verification.
3740

38-
## Multi-factor authentication
41+
## Multi-factor authentication workaround
3942

40-
Instead of using push notifications for multi-factor authentication, users can set up their multi-factor authentication to receive verification codes they can use to verify their identity. These verification codes are valid for 30 seconds and to use them, admins must enable their tenant to perform verification using Time-based One-Time Password (TOTP) verification codes.
43+
Instead of using push notifications for multi-factor authentication, users can set up their MFA to receive verification codes on their device that they can use to verify their identity. These verification codes are valid for 30 seconds and to use them, admins must enable their tenant to perform verification using Time-based One-Time Password (TOTP) verification codes.
4144

4245
## Availability
4346

0 commit comments

Comments
 (0)