Text File | Enforce License rule
This rule queries the specified CSV file containing a list of Active Directory or MS365 users and assigns licenses according to the Action section settings.
NOTE: The CSV-file must be in UTF-8 format in case of using letters with an accent: á, ä, é, í, ö, ü and etc.
When to use this rule
Use this rule when you need to enforce Microsoft 365 licenses to Active Directory or Microsoft 365 users specified in the CSV file.
This rule requires a source text file in the comma-separated variable format (CSV). You can use the template CSV files provided with the rule, or create a file in Microsoft Excel and export as CSV.
To use a template CSV file:
In the Query section, click the [...] button next to the Select Data Source setting.
Open the Templates folder.
Depending on the Account source system, select Enforce Office 365 License (Hybrid) or Enforce Office 365 License (Microsoft 365) CSV file.
Click Open.
The Query's source text file requires the following CSV (comma-separated value) format:
Hybrid users:
UserPrincipalName,DistinguishedName,SamAccountName,ObjectGuid
Joe.Smith@domain.com,"CN=Joe Smith,OU=IT,DC=domain,DC=com",jsmith,dd16cabd-b1a6-4fc4-b5b6-d86d8d8fca9e
Kelly.Jones@domain.com,"CN=Kelly Jones,OU=IT,DC=domain,DC=com",kjones,84da7c1e-69f8-48d9-afae-cc61bbf85be2Microsoft 365 users:
UserPrincipalName,ObjectGuid
Joe.Smith@domain.com,dd16cabd-b1a6-4fc4-b5b6-d86d8d8fca9e
Kelly.Jones@domain.com,84da7c1e-69f8-48d9-afae-cc61bbf85be2Rule Settings
| Setting Name | Description |
|---|---|
| Select data source |
Specify the text file to be imported. The […] (three dots) button allows the user to browse for the file and the Create/Edit button allows the creation or editing of the existing file in the built-in Data Source editor. |
| Data source anchor attribute | Select a column in the data source that contains the attribute value for identifying and mapping a computer. |
| Account source system | Choose whether the accounts in the CSV are from Hybrid or Microsoft 365. |
| User anchor attribute |
Automap looks for a user using attributes like DistinguishedName UserPrincipalName, and ObjectGUID.If you're using a different attribute, select it here. NOTE: Microsoft best practices suggest that AD and Office 365/Azure AD UPNs should match. |
| More Options | |
| Filter CSV data | Use this filter to remove rows from the imported file that meet specific conditions. |
| Properties to display | Each object property defined in this setting matches the column that will be displayed in the Web Portal for this web query.To display additional columns, add the required properties to the Properties to display list.To add extension attribute 1 that is synchronized from AD, you need to use a value like:"OnPremisesExtensionAttributes/extensionAttribute1~Extension Attribute 1" |
| Filter Office 365 users | Set filtering conditions here to hide unwanted data. |
| License options | Select which Microsoft 365 license plans and options to assign or revoke to Microsoft 365 user accounts.It is also possible to click Ignore to completely exclude the plan from the rule. In this case, this plan and its options won't be taken into consideration at all. If users already have assigned options from this plan, these options will keep. If users don't have options from this plan, these options won't be assigned. |
| All other licenses | Any licenses not specified in License options can either be ignored or unassigned. |
| Change Usage Location only if not set | It is possible to keep the current user's usage location or change it to a new one. |
| Usage Location | Select the usage location.If Microsoft 365 user accounts don't have a location attribute set, Microsoft 36 license won't apply to them, and the rule will stop with the error. If you use Usage Location from AD value for this setting, you must be sure all Active Directory user accounts, that fall under this rule this, have a location attribute set. |
Output Section
This section defines the output format of this rule.
To get more information about this section, please see the Rule Output section article.
Enforce/Schedule section
This section defines the schedule for how often to run the rule.
To get more information about this section, please see the Rule Enforce/Schedule section article.
Change History
| Version | Notes |
|---|---|
| 9.3.0 | The rule has been introduced in the product. |
Comments
0 comments
Please sign in to leave a comment.