Account/Authentication - Azure Active Directory - Ensure that Collaboration Invitations are Sent to Allowed Domains Only

By Ashwin Venugopal -

 






Summary

Users should be able to send collaboration invitations to allowed domains only.

Reason

If the allowed domains for collaborations are specified, external companies can be explicitly identified. Additionally, this prevents internal users from inviting unknown external users like personal accounts and give them access to resources. 

What If?

This could make harder collaboration if the setting is not quickly updated when a new domain is identified as "allowed".

How to?

From the Azure portal:
  1. Go to Azure Active Directory.
  2. Go to Users.
  3. Go to User Settings.
  4. Under External users, click on Manage external collaboration settings.
  5. Under Collaboration restrictions, choose allow invitations only to the specified domains (most restrictive), check the Target domains setting, and specify the domains allowed to collaborate.
Default Value: It is Allow invitations to be sent to any domain (most inclusive) and thus no domain is specified.

Monitor:

From the Azure portal:
  1. Go to Azure Active Directory.
  2. Go to Users.
  3. Go to User Settings.
  4. Under External users, click on Manage external collaboration settings.
  5. Under Collaboration restrictions, make sure that Allow invitations only to the specified domains (most restrictive) is selected. After this, ensure that Target domains is checked and that allowed domains are specified.













































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