From 84a1760d41fdce9beeb558b4fd259dbf1bdac739 Mon Sep 17 00:00:00 2001 From: Tanya Bittenmaster <30839220+tbit0001@users.noreply.github.com> Date: Thu, 7 Sep 2017 11:14:09 -0400 Subject: [PATCH] Update menu items --- ...ages-windows-defender-advanced-threat-protection.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-error-messages-windows-defender-advanced-threat-protection.md b/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-error-messages-windows-defender-advanced-threat-protection.md index 4ebf7ba43a..22467a0cfd 100644 --- a/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-error-messages-windows-defender-advanced-threat-protection.md +++ b/windows/threat-protection/windows-defender-atp/troubleshoot-onboarding-error-messages-windows-defender-advanced-threat-protection.md @@ -32,13 +32,13 @@ If you receive an error message, the Windows Defender ATP portal will provide de ## No subscriptions found -If while accessing the Windows Defender ATP portal you get a “No subscriptions found” message, it means the Azure Active Directory for the user, used to login to the portal, does not have a Windows Defender ATP license. +If while accessing the Windows Defender ATP portal you get a “No subscriptions found” message, it means the Azure Active Directory for the user, used to login to the portal, does not have a Windows Defender ATP license. Potential reasons: -- Windows E5 and Office E5 license may be being confused. These are not the same. -- The license was purchased but not provisioned to this Microsoft Azure Active Directory instance. - - It could be a license provisioning issue. - - It could be you inadvertantly provisioned the license to a different Microsoft Azure Active Directory than the one used for authentication into the service. +- Windows E5 and Office E5 license are not the same thing. Make sure you are capturing the correct information. +- The license was purchased but not provisioned to this Microsoft Azure Active Directory (AAD) instance. + - It could be a license provisioning issue. + - It could be you inadvertantly provisioned the license to a different Microsoft AAD than the one used for authentication into the service. For both cases you should contact Microsoft support.