Plan Your Identity & Authentication Solution (part 2)

By Ashwin Venugopal -

 



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




Directory Synchronization

It is known as the synchronization of directory identities or objects (users, groups, contacts, and computers) between two different directories, like your on-premises AD environment and Azure AD which can easily support online services like Microsoft 365. Although in Microsoft 365 directory synchronization is generally used to synchronize in one direction (i.e. from on-premises to Azure AD), but some features in Azure AD Connect permits it to write-back specific objects and attributes to the on-premises directory creating a sort of two-way synchronization. 

If you integrate your on-premises directories with Azure AD, it will allow your users to enhance productivity by reducing the amount of time spent in typing passwords for accessing both cloud and on-premises resources. The users and organizations can take following advantages from this integration:

  • Hybrid identity- A common hybrid identity can be offered across on-premises and cloud-based services along with a consistent group membership by leveraging AD and then connecting to Azure AD.

  • AD policies- The AD policies set through AD can be used by the administrators to help provide conditional access according to an application resource, device and user identity, network location, and multi-factor authentication without performing any additional task in the cloud.

  • Leverage identity- Users can readily leverage their common identity with the help of their accounts in Azure AD to Office 365, Intune, SaaS apps, and non-Microsoft applications.

  • Single-sign-on (SSO)- Users identities and information are protected as all the servers as well as services used in SSO are mastered and controlled on-premises, giving confidence to security.

  • Multi-factor authentication (MFA)- Security will have more confidence if they have the option to use strong authentication also known as multi-factor authentication (MFA), with the cloud service. 

  • Common identity model- Applications that can leverage the common identity model can be build with the help of developers integrating applications into on-premises AD while it is done (for examples, Azure AD App Proxy or Azure for Cloud-based applications).









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





Comments

Post a Comment

Popular posts from this blog

Query, Visualize, & Monitor Data in Azure Sentinel

By Ashwin Venugopal -
Image
  Azure Sentinel Workbooks Several ready for use templates are provided by the Azure Sentinel that can be used to create your own workbook and then modify them as needed for Contoso. Most of the data connectors it uses to ingest data come with their own workbooks, but better insight can be obtained by simply looking into the data that is being ingested by using tables and visualizations, including bar and pie charts. You can also make your own workbook easily by using this data from the beginning instead of using the predefined templates. Workbook Page You can easily access the workbook page from the Azure Sentinel from the navigation pane which consists of the: Workbook header- You can add a new workbook and review the saved workbooks as well as templates that are available on the workbook page. Templates section- You can access existing workbook templates on the Templates tab. You can save some of the workbooks for quick access and they will appear on the My Workbooks tab.  From the
Read more

Planning for Implementing SAP Solutions on Azure (Part 2 of 5)

By Ashwin Venugopal -
Image
  To read part 1 please click  here To read part 3 please click  here To read part 4 please click  here To read part 5 please click  here Load Balancing The load balancer uses probe ports to determine as well as route the traffic to an active DBMS node, but of there's any failover then the most common SAP application architecture can automatically reconnect against the private virtual IP address without the need for the SAP application to reconfigure it, while the load balancer redirect the traffic against the private virtual IP address without any need for the SAP application to reconfigure. The loaf balancer also offers an option of DirectServerReturn which if configured, can help in directing the traffic from the DBMS VM to the SAP application layer directly to the application layer without routing through the load balancer. But, if it isn't configured, then the return traffic to the SAP application layer is routed through the load balancer. You can also use Azure Load Balan
Read more

Work with String Data Using KQL Statements

By Ashwin Venugopal -
Image
  Extract Data from Unstructured String Fields Unstructured string fields often contains the Security log data and requires parsing to extract data. There are multiple ways of pulling information from string fields in KQL and the two primary operators used are extract and parse.  Extract It gets a match for a regular expression from a text string. You can convert the extracted substring to the indicated type.  Arguments regex- A regular expression. captureGroup- A positive int constant indicating the capture group to extract. 0 stands for the entire match, 1 for the value matched by the first '('parenthesis')' in the regular expression, 2 or more for subsequent parenthesis.  text- A string to search. typeLiteral- An optional type literal. If provided, the extracted substring is converted to this type.  Returns If regex finds a match in text- the substring matched against the indicated capture group captureGroup, optionally converted to typeLiteral. If there's no mat
Read more