The blog describes some troubleshooting steps you can take if you have followed the process to on-board Windows 10 to WDATP (as described here), but the devices are not appearing in the Machine List on Windows Defender ATP portal
Open an elevated command prompt and run
sc qc diagtrack
In my case the service was running without errors
This blog describes steps required to on-board a device onto Windows Defender Advanced Threat Protection (WDATP), and how to verify the on-boarding was successfully.
On-boarding
There may be times where you need to do some housekeeping on your Office 365 licenses. Users may have left, for example, had their active directory accounts disabled, but are still consuming a license in Office 365. Here is a simple powershell one-line that will output a report to CSV.
Connect powershell to Azure AD for your Office 365 subscription as described here and run the following
During an Office 365 / Exchange Online migration, you may have a requirement to update the recipient filter of any dynamic distribution group.
In my case, I needed to do this because the dynamic distribution group used filters to include only mailboxes. But mailboxes that are migrated to Office 365 become mail-enabled users in the on-premises directory. This can cause issues with certain members of a dynamic distribution group not receiving email messages. The issue is described here
In a recent project I came across a scenario where there was a requirement to synchronize the built-in Administrator account from the on-premise Active Directory into Azure AD. Reason being was the built-in Administrator account was mailbox enabled, and there was a requirement to migrate the mailbox to Exchange Online (Office 365)
I came across this issue recently and wanted to shared my experience
Environment
The organization has the following configuration
Requirement
As per the supported topologies for Azure AD Connect here this can be achieved using the same instance of Azure AD Connect. No forest trust required, but some pre-req’s are required as outlined here including Firewall ports (listed here) , DNS Name resolution (using a Conditional Forwarder -see discussion here) and an account in Forest B with Enterprise Admins permissions.
Every user mailbox in Exchange Online requires an Office 365 license to be assigned to the user. Often when migrating from Exchange On-premises, there are more user mailboxes than actual users, and more importantly, more user mailboxes than Office 365 licenses. In this scenario, a number of options can be considered including:
In this blog post, I’ll demonstrate step by step how to enable, verify and test litigation hold in Office 365. I’ll be focusing specifically on the Exchange Online workload.
You can enable litigation hold for a mailbox by running the following command from the Exchange Online shell (note: steps to connect PowerShell to Exchange Online can be found here)
In this blog post I want to share some tips for identifying issues when running the Office 365 Hybrid Configuration Wizard (HCW), available here .
Specifically,
In my experience, network relates issues are the most common cause of HCW failures, and that is where this blog post will focus. Most corporate networks have firewall and / or proxy restrictions in place. There are very specific network requirements for connectivity to Office 365 as detailed here .
Problem
I came across this issue while working on an Exchange Hybrid deployment. During the testing phase, I successfully migrated mailboxes from Exchange 2010 to Exchange Online. However, when I migrated a mailbox from Exchange 2010 to Exchange 2016, my Outlook client could not connect to its mailbox and would continually prompt for login credentials