The Active Directory Recycle Bin allows Domain Administrators to recover Active Directory objects that may have been accidentally deleted. However, the recycle bin is not enabled by default, so it is important to enable the recycle bin before a restore is needed.

While the Microsoft 365 admin center GUIs are decent, there are many Microsoft 365 management tasks that are better suited for PowerShell. However, before you can start scripting, you must first establish a connection to your Microsoft 365 tenant.

In this scenario, an on-premise active directory user was created and synced with Microsoft 365. The Microsoft 365 user has an Exchange Online mailbox, but this mailbox is not visible in the on-premise Exchange Admin Center.

Converting a user mailbox to a shared mailbox in a hybrid Exchange environment can be frustrating. Fortunately, there is a PowerShell command available that makes the entire process much simpler.

Adding users and mailboxes changes slightly when working in hybrid Exchange environments.While adding a user in ADUC and licensing the user in Microsoft 365 is possible, the user's Exchange attributes will never be synced with the on-premise environment.

We often need to allow users to access executables that CageFS does not allow by default. There are a couple of ways to accomplish this depending on if the package was compiled manually or installed via a package manager.

The "repadmin" tool provides an easy way to monitor replication status, identify replication issues, and force replication inside of your AD forest.

We see this one a lot: a domain controller that either crashed or was uncleanly demoted, but never removed from the Active Directory forest. Since the original domain controller is gone, we'll need to manually remove it from Active Directory.

Sometimes you need to replicate changes between your on-premise Active Directory and Azure, but don't want to wait for the next scheduled sync. In these cases, the ADSync PowerShell module provides a very easy way to force synchronization.

Filtering what objects are synced to Azure AD is a common request and there are many instances where filtering by OU just doesn't cut it. One option is to filter users by their UPN suffix so that only users with the public FQDN as their UPN suffix are synced to Azure AD.