Configure & Manage Synchronized Identities (part 2 of 4)

By Ashwin Venugopal -

 





To read part 1, please click here
To read part 3, please click here
To read part 4, please click here 



Set Up Azure AD Connect

You can easily install Azure AD Connect by using either Express or Custom setup.

Azure AD Connect Express Setup

It is the most common option used by 90% of all the new installations as it can offer the configuration that works for the most common customer scenarios. It assumes:
  • You have a single AD forest on-premises.
  • You have an enterprise administrator account that can be used for the installation.
  • You have less than 100,000 objects in your on-premises AD. 

You get:

  • Password hash synchronization from on-premises to Azure AD for single sign-on.
  • A configuration that synchronizes users, groups, contacts, and Windows 10 computers. 
  • Synchronization of all eligible objects in all domains and all OUs.
  • Automatic upgrade is enabled to ensure you always use the latest available version. 

Azure AD Connect Custom Setup

It can be used when:
  • You don't have access to an enterprise admin account in AD.
  • You have more than one forest or you plan to synchronize more than one forest in the future.
  • You have domains in your forest not reachable from the Connect Server.
  • You plan to use federation or pass-through authentication for user sign-in.
  • You have more than 100,000 objects and need to use a full SQL server.
  • You want to use group-based filtering and not only domain or OU-based filtering. 

Azure AD Connect Health

If offers robust monitoring of your on-premises identity infrastructure while allowing you to maintain a reliable connection to Office 365 and Microsoft Online Services. It is as simple as installing an agent on each of your on-premises identity servers. You have to perform following tasks before starting with Azure AD Connect Health:
  1. Sign in to Azure portal.
  2. Type "Azure AD Connect Health" in All Services box and select it.
  3. Use the Quick start options or go directly to the sync services you are using.  

As Azure AD Connect Health is a part of Azure AD Premium, it requires the necessary licenses to be available.










To read part 1, please click here
To read part 3, please click here
To read part 4, please click here 












Comments

Post a Comment

Popular posts from this blog

Deployment (Part 3)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 2, please click  here Microsoft Monitoring Agent (MMA) MMA is used across multiple Microsoft solutions and has undergone a few name changes as its features and functionality have evolved. If it is being considered to be used, then following areas should be covered during a Microsoft Sentinel deployment project: Consider the timelines and the strategy for a migration to AMA (Azure Monitor Agent) before the MMA end-of-life.  Consider the central deployment and management methodology for MMA. Determine which endpoints are in scope for deployment as these affect the log ingestion volume significantly.  Azure Monitor Agent (AMA) Organizations with MMA as the main Microsoft Sentinel agent should start planning the migration to AMA as soon as possible to avoid a rushed migration. One of the main advantages of AMA is the ability to control the log collection policy centrally and apply different policies against different...
Read more

Deployment (Part 1)

By Ashwin Venugopal -
Image
  To read part 2, please click  here To read part 3, please click  here Azure Resources Microsoft Sentinel needs following resources to be created: Subscription (if a dedicated subscription(s) will be used) Resource group(s) Log Analytics workspace(s) Automation rules/playbook Alert rules Workbooks Microsoft Sentinel offers hundreds of alert rules, workbooks, and automation playbook templates along with hunting scripts. The templates can be used to activate/deploy schedule alerts, create customized dashboards, create automation playbooks and perform threat-hunting activities. Generally, once deployed, the resources created have to be adjusted to match the existing environment, configure local credentials, etc. Methods of deployment: Manual- Administrator can manually configures the Microsoft Sentinel resources with the help of Azure portal. Any manual process has the inherent risks of human operator error, lack of compliance with potential change control procedures, and u...
Read more

Deployment (Part 2)

By Ashwin Venugopal -
Image
  To read part 1, please click  here To read part 3, please click  here Microsoft Sentinel Content Hub Content in Microsoft Sentinel includes any of the following types: Data connectors offer log ingestion from different sources into Microsoft Sentinel. Parsers give log formatting/transformation into ASIM formats, supporting usage across various Microsoft Sentinel content types and scenarios. Workbooks provide monitoring, visualization, and interactively with data in Microsoft Sentinel, highlighting meaningful insights for users.  Analytics rules give alerts that point to relevant SOC actions via incidents.  Hunting Queries are used by SOC teams to proactively hunt for threats in Microsoft Sentinel. Notebooks help SOC teams in using advanced hunting features in Jupyter and Azure Notebooks. Watchlists support the ingestion of specific data for enhanced threat detection and reduced alert fatigue.  Playbooks and Azure Logic Apps Custom Connectors provide featu...
Read more