Get Live Help
A guest user is an Azure Active Directory Business-to-Business account which is utilized to provide seamless collaboration between the Microsoft Cloud organizations.
For more context and details check out Microsoft’s document on the topic, What is guest user access in Azure Active Directory B2B?
Yes, Power365 Directory Sync provides create, update and delete capabilities to keep your multiple identities, objects and properties in sync for short-term and long-term integration needs.
There are two (2) new additional options to create users in a target cloud directory, highlighted below. The image shows the Template wizard where you may manage how users are created.
Figure 1: Example Template Wizard - Create New Users – Guest Options
The Guest User option (see figure 1) will create a user object with the type of Guest within the destination directory configured in the workflow. This user’s password will be set and managed within the target directory management controls. This user’s UPN, Display Name and email address will be constructed based on the template mapping controls configured within the workflow.
The Guest Invite option (see figure 1) will create a user object with the type of Guest within the destination directory configured in the workflow and immediately send an invitation to the source email user account. This user’s UPN will be constructed automatically by Microsoft to meet their requirements for B2B functionality. This user’s password will not be set and will continue to be managed from the source directory management tools and administrators. All other attributes set during creation will be determined by the template mapping controls configured within the workflow.
Yes, Microsoft provides numerous methods for managing invitations. For more details, see the Azure Active Directory B2B documentation.
Yes, Power365 Directory Sync can match and update existing Guest user types in Active Directory and Azure AD.
To match a source user object to a target Guest user object can sometimes be challenging because depending on the type of target Guest user object, there may not be a readily available attribute or property that can be used for an exact match to ensure an accurate match.
How to identify unique attributes for Matching to Guest Users
Before synchronization, you must first decide how to derive the matching attribute pairs between the source user object and target guest object. In other words, what parameters in your environment are unique to your external collaborators? Determine a parameter that distinguishes these external collaborators from members of your own organization.
A common approach to resolve this is to:
- Designate an unused attribute (for example, extensionAttribute1) to use as the source attribute that will match to a unique identifier attribute, such as email, in the target.
- Next construct the value for that attribute from other source properties, to create a unique identifier that will be found in the target. For example, use the email address of the source user to construct the extensionAttribute1 value as Source Local Part @ Target Domain.
Yes, Power365 Directory Sync supports the creation of local user objects for this purpose. Simply configure the template mappings to set the attribute value of the predetermined attributed which will be used by Azure AD Connect to set the UserType = Guest in the cloud object. If you are using a different method within Azure AD Connect, adjust your mapping rules to fit your needs.
You can use Azure AD Connect to sync the accounts to the cloud as Azure AD B2B users (that is, users with UserType = Guest). This enables your users to access cloud resources using the same credentials as their local accounts, without giving them more access than they require.
For more information about How to grant local users access to cloud apps read this Microsoft article on the topic.
For details on How to enable synchronization of UserType for Azure AD Connect then please read this Microsoft document.
How To Use Guest Users in Power365 Directory Sync
Guest Users in Power365 Tenant-to-Tenant
What is guest user access in Azure Active Directory B2B?
Azure Active Directory B2B best practices
Azure Active Directory B2B documentation
Properties of an Azure Active Directory B2B collaboration user
Quickstart: Add guest users to your directory in the Azure portal
Add guests to the global address list
If a workflow is a series of action steps, an environment is the receiver of those actions. On the Select Environments screen you will choose two or more environments that the workflow will take actions against. You need at least two so that you have at least one source and one target, but you can choose several in a more complex migration scenario. For example, you may choose to read from two different environments as sources, to be written to a single target environment.
To manage environments, simply open the left navigation menu and click Environments, located under Settings, see figure 1.
Figure 1: Directory Sync Setup and Settings Menu
To add a local environment:
On the Environments page, Click the New button. The Select your Environment type page appears.
Select Local and click Next.
Enter a name for your environment and click Next.
- Enter a name for your agent and click Next.
Enter values in the following fields:
Target Domain Controller IP Address – The IP address of the target Domain Controller.
Target Domain Controller Ping Interval - The number of seconds the script will sleep between pings to the defined target domain controller. The default value is 300 seconds.
Timeout Before Job Failure – The number of minutes to wait after Credential Cache job is downloaded by the agent before marking the job a failure due to timeout. The default value is 180 minutes.
Timeout for User Credential Prompt – The number of minutes to prompt the user with a dialog box to enter their target domain credentials for caching. The default value is 5 minutes
Click Save Profile. The Credential Cache Profile is added to the list.
Select an environment in the Environments table and then click Details. On the Details page, click the Export button to download a CSV file of the Users, Groups, Contacts, or Devices.
Select an environment in the Environments table and then click Details. On the Details page, select an object in the table and click the Unmatch button. The Match Status for the object will change to "Unmatched" and the object will not be synchronized.
The Unmatch action is not supported for objects belonging to the Tenant-to-Tenant project and registered devices.
Select a local environment in the Environments table and then click Password Logs or Discovery Logs to export a CSV with password or discovery information.
Select a local environment in the Environments table and then click Discover to begin the discovery process for the environment.
Select a cloud environment in the Environments table and then click Settings. Then select the Object Filter tab to view the filter options. Uncheck the object types you wish to exclude. Options to exclude unlicensed and disabled accounts are also available. Click Attribute Filters to build filters that allow you to be more specific as to which object(s) to sync. Select the Filter Groups tab to enable Group filters.
Alerts may be added to keep administrators informed of the success completion and/or failure of any workflow. Alerts are delivered as status emails to the designated recipients. For each workflow choose the previously created alerts or add a new alert. Easily add multiple recipients, by separating the addresses with a semicolon.
To manage workflow alerts, simply open the left navigation menu and click Alerts, located under Settings, see figure 1.
Figure 1: Directory Sync Setup and Settings Menu
Follow these steps to create a new workflow alert.
- Login to Power365.
- Navigate to Alerts.
- Click New.
- Enter a Name, click Next.
- Enter recipients. To add multiple recipients, separate addresses with a semicolon ( ; ).
- Click Next.
- Choose Language preference, click Next.
- Choose which events trigger alerts.
- Choose Workflow Failure at a minimum.
- Do not choose Local Agent Offline for a Cloud only workflows and environments.
- Click Next.
- Click Finish.
Follow these steps to add an alert to an existing workflow.
What workflow events can generate an alert?
You can select to have an email notification sent when the workflow finishes for the following events:
- Workflow Completion - A notification will be sent each time your workflow completes successfully.
- Workflow Failure - A notification will be sent each time your workflow completes successfully.
- Local Agent Offline - A notification will be sent each time local agents go offline.
Alerts can be edited on the Alerts page by selecting an Alert in the table and clicking "Settings."
Active alerts can be disabled on the Alerts page by selecting the alert in the table and clicking "Disable." Disabled alerts can be activated on the Alerts page by selecting the alert in the table and clicking "Enable."