Microsoft support without validation

These logs can contain personal data such as email addresses, server addresses, or IP addresses. They also can contain device data such as device name and operating system version. Any personal data collected is limited to info needed to help troubleshoot app issues.

You can browse these log files in the app at any time to see the info being gathered. If you send your log files, Authentication app engineers will use them only to troubleshoot customer-reported issues. Your usage helps us determine where we can improve the apps in ways that are important to you. You see a notification of this data collection when you use the app for the first time. You can turn this setting on or off at any time. A: When you open Authenticator, you'll see your added accounts as tiles.

Your work or school accounts and your personal Microsoft accounts will have six or eight digit numbers visible in the full screen view of the account accessed by tapping the account tile. You'll use these codes as single-use password to verify that you are who you say you are.

After you sign in with your username and password, you'll type in the verification code that's associated with that account.

For example, if you're Katy signing in to your Contoso account, you'd tap the account tile and then use the verification code Tap the Contoso account tile.

After you tap the Contoso account tile, the verification code is visible in full screen. A: You might see a second timer counting down next to your active verification code. This timer is so that you never sign in using the same code twice. Unlike a password, we don't want you to remember this number.

The idea is that only someone with access to your phone knows your code. A: Some organizations require Authenticator to work with single sign-on and to protect organizational resources. In this situation, the account isn't used for two-step verification and shows up as gray or inactive. This type of account is frequently called a "broker" account. A: Your org might require you to register the device to track access to secured resources, such as files and apps.

They also might turn on Conditional Access to reduce the risk of unwanted access to those resources. You can unregister your device in Settings , but you may lose access to emails in Outlook, files in OneDrive, and you'll lose the ability to use phone sign-in. Q: Do I need to be connected to the Internet or my network to get and use the verification codes?

A: The codes don't require you to be on the Internet or connected to data, so you don't need phone service to sign in. Additionally, because the app stops running as soon as you close it, it won't drain your battery.

Q: Why do I only get notifications when the app is open? When the app is closed, I don't get notifications. A: If you're getting notifications, but not an alert, even with your ringer on, you should check your app settings. Make sure the app is turned on to use sound or to vibrate for notifications.

If you don't get notifications at all, you should check the following conditions:. Is your phone in Do Not Disturb or Quiet mode? These modes can prevent apps from sending notifications. Can you get notifications from other apps? If not, it could be a problem with the network connections on your phone, or the notifications channel from Android or Apple. You can try to resolve your network connections through your phone settings. You might need to talk to your service provider to help with the Android or Apple notifications channel.

Can you get notifications for some accounts on the app, but not others? If yes, remove the problematic account from your app, add it again allowing notifications, and see if that fixes the problem. If you tried all of these steps and are still having issues, we recommend sending your log files for diagnostics.

After that, go to the Microsoft Authenticator app forum and tell Microsoft the problem you're seeing and the steps you tried. A: You can set up notifications for your work or school account if allowed by your administrator or for your personal Microsoft account. Notifications won't work for third-party accounts, like Google or Facebook. To switch your personal account over to notifications, you'll have to re-register your device with the account.

Go to Add Account , select Personal Microsoft Account , and then sign in using your username and password. For your work or school account, your organization decides whether or not to allow one-click notifications. If your work or school uses Azure AD accounts, they are able to turn off this feature. Q: I got a new device or restored my device from a backup. How do I set up my accounts in Authenticator again?

A: If you turned on Cloud Backup on your old device, you can use your old backup to recover your account credentials on your new iOS or an Android device. For more info, see the Backup and recover account credentials with Authenticator article. Q: I lost my device or moved on to a new device. How do I make sure notifications don't continue to go to my old device?

A: Adding Authenticator to your new device doesn't automatically remove the app from your old device. Even deleting the app from your old device isn't enough. You must both delete the app from your old device AND tell Microsoft or your organization to forget and unregister the old device.

To remove the app from a device using a work or school Microsoft account, go to the two-step verification area of either your My Apps page or your organization's company portal to turn off verification for your old device. Tap Remove account to remove the account from the app.

If you have a device that is registered with your organization, you might need an extra step to remove your account. To enable encryption to be used when a certificate hasn't been provisioned on the server, SQL Server Configuration Manager can be used to set both the Force Protocol Encryption and the Trust Server Certificate options. In this case, encryption will use a self-signed server certificate without validation if no verifiable certificate has been provisioned on the server.

Applications may also use the "TrustServerCertificate" keyword or its associated connection attribute to guarantee that encryption takes place.

For example, if Force Protocol Encryption isn't set for the client, an application may request encryption itself.

To guarantee encryption even when a server certificate hasn't been provisioned, an application may request encryption and TrustServerCertificate. However, if TrustServerCertificate isn't enabled in the client configuration, a provisioned server certificate is still required. The following table describes all cases:. The preceding table only provides a guide on the system behavior under different configurations. For secure connectivity, ensure that the client and server both require encryption.

When using service components, it accepts true or false values; false is the default. In addition, a new connection string keyword, "TrustServerCertificate", has been added. It accepts yes or no values; "no" is the default. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode.

Is this page helpful? Please rate your experience Yes No. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. Not enough pictures. Any additional feedback?