Attribute mapping in Azure AD Connect

You can use the cloud sync attribute mapping feature to map attributes between your on-premises user or group objects and the objects in Azure AD.

Synchronization Rules in Azure AD Connect.

You can use the synchronization rule editor to edit or create a new synchronization rule. You need to be an advanced user to make changes to synchronization rules.

What is Synchronization Service Manager in Azure AD Connect ?

The Synchronization Service Manager UI is used to configure more advanced aspects of the sync engine and to see the operational aspects of the service.

You start the Synchronization Service Manager UI from the start menu. It is named Synchronization Service and can be found in the Azure AD Connect group

Administrative units in Azure Active Directory

An administrative unit is an Azure AD resource that can be a container for other Azure AD resources. An administrative unit can contain only users, groups, or devices.

Administrative units restrict permissions in a role to any portion of your organization that you define. You could, for example, use administrative units to delegate the Helpdesk Administrator role to regional support specialists, so they can manage users only in the region that they support.

Users can be members of multiple administrative units. For example, you might add users to administrative units by geography and division; Megan Bowen might be in the "Seattle" and "Marketing" administrative units.

Manual to Automatic Microsoft Azure AD license assignment!

Manual to Automatic Microsoft Azure AD license assi

How to Create Microsoft 365 Groups -Azure Active Directory?

Microsoft 365 Groups is the foundational membership service that drives all teamwork across Microsoft 365. With Microsoft 365 Groups, you can give a group of people access to a collection of shared resources. These resources include:

• A shared Outlook inbox
• A shared calendar
• A SharePoint document library
• A Planner
• A OneNote notebook
• Power BI
• Yammer (if the group was created from Yammer)
• A Team (if the group was created from Teams)
• Roadmap (if you have Project for the web)
• Stream

HOW TO CREATE DYNAMIC GROUPS IN AZURE ACTIVE DIRECTORY?

You can create attribute-based rules to enable dynamic membership for a group in Azure Active Directory (Azure AD), part of Microsoft Entra. Dynamic group membership adds and removes group members automatically using membership rules based on member attributes. This article details the properties and syntax to create dynamic membership rules for users or devices. You can set up a rule for dynamic membership on security groups or Microsoft 365 groups.

When the attributes of a user or a device change, the system evaluates all dynamic group rules in a directory to see if the change would trigger any group adds or removes. If a user or device satisfies a rule on a group, they're added as a member of that group. If they no longer satisfy the rule, they're removed. You can't manually add or remove a member of a dynamic group.

• You can create a dynamic group for devices or for users, but you can't create a rule that contains both users and devices.
• You can't create a device group based on the user attributes of the device owner. Device membership rules can reference only device attributes.

Azure AD Bulk Users Management - Crete,Invite,Delete.

Managing users within the Azure Portal can be a tiresome process if you have many users. Creating, inviting, or deleting users one at a time is not practical if you need to manage hundreds or thousands of them. Fortunately, Azure provides a way to manage users in bulk.

The Azure Portal allows you to upload a Comma-separated value (CSV) file with user information so that you can Create, Invite, or Delete many users at once.

In this article, I will show you how to use these bulk operations to create users. The process is nearly identical for inviting and deleting users. Only the CSV template file is different.

Manage Groups in Azure Active Directory.

ManageGroups in Azure AD. 

Manage Users in Azure Active Directory

Azure AD defines users in three ways:

• Cloud identities: These users exist only in Azure AD. Examples are administrator accounts and users that you manage yourself. Their source is Azure Active Directory or External Azure Active Directory if the user is defined in another Azure AD instance, but needs access to subscription resources controlled by this directory. When these accounts are removed from the primary directory, they are deleted.

• Directory-synchronized identities: These users exist in an on-premises Active Directory. A synchronization activity that occurs via Azure AD Connect brings these users in to Azure. Their source is Windows Server AD.

• Guest users: These users exist outside Azure. Examples are accounts from other cloud providers and Microsoft accounts, such as an Xbox LIVE account. Their source is Invited user. This type of account is useful when external vendors or contractors need access to your Azure resources. Once their help is no longer necessary, you can remove the account and all of their access.

Pass-Through Authentication - Step By Step

What is Azure Active Directory Pass-through Authentication?

Azure Active Directory (Azure AD) Pass-through Authentication allows your users to sign in to both on-premises and cloud-based applications using the same passwords. This feature provides your users a better experience - one less password to remember, and reduces IT helpdesk costs because your users are less likely to forget how to sign in. When users sign in using Azure AD, this feature validates users' passwords directly against your on-premises Active Directory.

Key benefits of using Azure AD Pass-through Authentication

• Great user experience
  • Users use the same passwords to sign into both on-premises and cloud-based applications.
  • Users spend less time talking to the IT helpdesk resolving password-related issues.
  • Users can complete self-service password management tasks in the cloud.
• Easy to deploy & administer
  • No need for complex on-premises deployments or network configuration.
  • Needs just a lightweight agent to be installed on-premises.
  • No management overhead. The agent automatically receives improvements and bug fixes.
• Secure
  • On-premises passwords are never stored in the cloud in any form.
  • Protects your user accounts by working seamlessly with Azure AD Conditional Access policies, including Multi-Factor Authentication (MFA), blocking legacy authentication and by filtering out brute force password attacks.
  • The agent only makes outbound connections from within your network. Therefore, there is no requirement to install the agent in a perimeter network, also known as a DMZ.
  • The communication between an agent and Azure AD is secured using certificate-based authentication. These certificates are automatically renewed every few months by Azure AD.
• Highly available
  • Additional agents can be installed on multiple on-premises servers to provide high availability of sign-in requests.