Application cases for SharePoint Online user account
Example:
Set up guest access to a site collection with read-only permissions. To do this, a SharePoint Online user account is added. The Azure Active Directory Guests group is assigned as authentication object to the user account. Jo User1 owns an Azure Active Directory user account, which is a member in this group. They can log in to the site collection with this and obtain all the SharePoint Online user account's permissions.
Jan User3 also obtain a guest login for the site collection. They own an Azure Active Directory user account in the same domain. In the Web Portal, they request membership of the Azure Active Directory Guests group. Once the request is granted approval and assigned, they can log in on the site collection.
SharePoint Online access permissions are supplied in different ways in the One Identity Manager, depending on the referenced authentication object.
Case 1: The associated authentication object is a group. The authentication system is managed in One Identity Manager. (Default case)
-
The user account represents an Azure Active Directory group. This group can be assigned in the One Identity Manager as authentication object.
-
The user account cannot be assigned to an identity. This means, the user account can only become a member in SharePoint Online roles and groups through direct assignment.
-
Before an identity can log in to the SharePoint Online system, they require an Azure Active Directory user account. This user account must be a member of the Azure Active Directory group that is used as an authentication object.
-
A new SharePoint Online user account can be created manually.
-
The user account cannot be managed through an account definition.
Case 2: The authentication object is a user account. The authentication system is managed in One Identity Manager.
-
The user account represents an Azure Active Directory user account. The user account is not assigned as an authentication object in One Identity Manager.
-
The SharePoint Online user account can be assigned to an identity. This means that the user account can become a member in SharePoint Onlineroles and groups through inheritance and direct assignment.
If an authentication object is assigned, the connected identity is found through the authentication object.
If there is no authentication object assigned, the identity can be assigned automatically or manually. Automatic identity assignment depends on the TargetSystem | SharePointOnline | PersonAutoFullsync and TargetSystem | SharePointOnline | PersonAutoDefault configuration parameters.
-
A new SharePoint Online user account can be manually created or by using an account definition. The Azure Active Directory user account used as the authentication object must belong to a domain trusted by the referenced authentication system.
-
The user account can be managed through an account definition.
For more information about identity handling and administration, see the One Identity Manager Target System Base Module Administration Guide.
Supported user account types
Different types of user accounts, such as default user accounts, administrative user accounts, service accounts, or privileged user accounts, can be mapped in One Identity Manager.
The following properties are used for mapping different user account types.
-
Identity type
The Identity type property (IdentityType column) is used to describe the type of user account.
Table 11: Identity types of user accounts
|
Primary identity |
Identity's default user account. |
Primary |
|
Organizational identity |
Secondary user account used for different roles in the company, for example for subcontracts with other functional areas. |
Organizational |
|
Personalized administrator identity |
User account with administrative permissions, used by an identity. |
Admin |
|
Sponsored identity |
User account used for a specific purpose. For example, for training purposes. |
Sponsored |
|
Shared identity |
User account with administrative permissions, used by multiple identities. |
Shared |
|
Service identity |
Service account. |
Service |
-
Privileged user account
Privileged user accounts are used to provide identities with additional privileges. This includes administrative user accounts or service accounts, for example. The user accounts are labeled with the Privileged user account property (IsPrivilegedAccount column).
Detailed information about this topic
Default user accounts
Normally, each identity obtains a default user account, which has the permissions they require for their regular work. The user accounts are linked to the identity. By default, the link between identity and SharePoint Online user account is set up through the authentication objects to which the user account is assigned. Alternatively, identities can also be directly linked to the user accounts. Such user accounts can be managed through account definitions. The effect of the link and the scope of the identity’s inherited properties on the user accounts can be configured through an account definition and its manage levels.
To create default user accounts through account definitions
-
Create an account definition and assign the Unmanaged and Full managed manage levels.
-
Specify how an identity's temporary deactivation, permanent deactivation, deletion, and security risks affect its user accounts and group memberships at each manage level.
-
Create a formatting rule for IT operating data.
You use the mapping rule to define which rules are used to map IT operating data for user accounts and which default values are used if no IT operating data can be determined through an identity's primary roles.
The type of IT operating data required depends on the target system. The following setting are recommended for default user accounts:
-
In the mapping rules for the IsGroupAccount_Group and IsGroupAccount_RLAsgn columns, use the default value 1 and set the Always use default value option.
-
In the mapping rule for the IdentityType column, use the default value Primary and enable Always use default value.
-
Enter the effective IT operating data for the target system. Select the concrete target system under Effects on.
Specify in the departments, cost centers, locations, or business roles that IT operating data should apply when you set up a user account.
-
Assign the account definition to identities.
When the account definition is assigned to an identity, a new user account is created through the inheritance mechanism and subsequent processing.
Related topics
Administrative user accounts
An administrative user account must be used for certain administrative tasks. Administrative user accounts are usually predefined by the target system and have fixed names and login names, such as Administrator.
Administrative user accounts are imported into One Identity Manager during synchronization.
NOTE: Some administrative user accounts can be automatically identified as privileged user accounts. To do this, in the Designer, enable the Mark selected user accounts as privileged schedule.
Related topics
