Automatically assign Microsoft 365 licenses

Using Adaxes you can completely automate the process of provisioning and deprovisioning accounts in Microsoft 365. In this tutorial, you will learn how to configure Adaxes to automatically assign Microsoft 365 licenses to new users. Also, you will learn how to assign different licenses to different users based on if-else rules.

For information on how to automate the configuration of mailboxes in Microsoft 365, see Automate Exchange mailbox configuration.

To automatically perform actions when a certain event takes place in your directory, you need to use business rules. Adaxes provides a built-in business rule, After user creation that is triggered after a new user account is created. You can use the rule to assign Microsoft 365 licenses to new users.

  1. For Adaxes to connect to your Microsoft 365 organization, you need to register your Microsoft 365 tenant.

    For details, see Register Microsoft 365 tenant.

  2. Launch Adaxes Administration console.

     How {id=collapse1}
    • On the computer where Adaxes Administration console is installed, open Windows Start menu.

    • Click Adaxes Administration Console.

  3. Expand Adaxes service \ Configuration \ Business Rules \ Builtin and select After user creation.

    For details on how to configure and activate the business rule, see Automate user provisioning.

    Alternatively, you can create a separate business rule that will assign Microsoft 365 licenses upon user creation.

     How {id=how_to_create_business_rule}
    • In Adaxes Administration console, right-click your Adaxes service, point to New and click Business Rule.

    • Enter a name for the new business rule and click Next.

    • On the Triggering Operation step, select User.

    • Select After and then select creating a user.

    • Click Next and follow instructions of the wizard.

  4. Double-click the Activate a Microsoft 365 account action.


    Location determines the Microsoft datacenter to use and the Microsoft 365 services available to users. By default, the location
    is set to %c%.

    Value reference %c% is replaced with the value of the Country property of the user. If country is not specified for a user, the value reference will be replaced with an empty value, and user location in Microsoft 365 will not be set.

    Since Microsoft 365 does not allow assigning licenses to users whose location is not specified, it is recommended to make the Country property required.

     How {id=property_patterns_how}
    • Select the built-in User property pattern.

    • Right-click Country and then click Edit in the context menu.

    • Select checkbox The property is required.

    • Optionally, specify a default country.

    • If necessary, configure the list of available countries.

    • Click OK and then click Save changes.

    If you want to set user location based on another property, use a value reference for the property you need instead of %c%. For example, if user location is stored in Extension Attribute 1, use the following value reference: %extensionAttribute1%.

    To set the same location for all users, specify a 2-letter country code (e.g. US, DE, CA) in the Location field.

     Country codes {id=country_codes}
    Country Country code
    Afghanistan AF
    Aland Islands AX
    Albania AL
    Algeria DZ
    American Samoa AS
    Andorra AD
    Angola AO
    Anguilla AI
    Antarctica AQ
    Antigua and Barbuda AG
    Argentina AR
    Armenia AM
    Aruba AW
    Australia AU
    Austria AT
    Azerbaijan AZ
    Bahamas BS
    Bahrain BH
    Bangladesh BD
    Barbados BB
    Belarus BY
    Belgium BE
    Belize BZ
    Benin BJ
    Bermuda BM
    Bhutan BT
    Bolivia, Plurinational State of BO
    Bonaire, Sint Eustatius and Saba BQ
    Bosnia and Herzegovina BA
    Botswana BW
    Bouvet Island BV
    Brazil BR
    British Indian Ocean Territory IO
    Brunei Darussalam BN
    Bulgaria BG
    Burkina Faso BF
    Burundi BI
    Cambodia KH
    Cameroon CM
    Canada CA
    Cabo Verde CV
    Cayman Islands KY
    Central African Republic CF
    Chad TD
    Chile CL
    China CN
    Christmas Island CX
    Cocos (Keeling) Islands CC
    Colombia CO
    Comoros KM
    Congo CG
    Congo, the Democratic Republic of the CD
    Cook Islands CK
    Costa Rica CR
    Cote d'Ivoire CI
    Croatia HR
    Cuba CU
    Curacao CW
    Cyprus CY
    Czech Republic CZ
    Denmark DK
    Djibouti DJ
    Dominica DM
    Dominican Republic DO
    Ecuador EC
    Egypt EG
    El Salvador SV
    Equatorial Guinea GQ
    Eritrea ER
    Estonia EE
    Ethiopia ET
    Falkland Islands (Malvinas) FK
    Faroe Islands FO
    Fiji FJ
    Finland FI
    France FR
    French Guiana GF
    French Polynesia PF
    French Southern Territories TF
    Gabon GA
    Gambia GM
    Georgia GE
    Germany DE
    Ghana GH
    Gibraltar GI
    Greece GR
    Greenland GL
    Grenada GD
    Guadeloupe GP
    Guam GU
    Guatemala GT
    Guernsey GG
    Guinea GN
    Guinea-Bissau GW
    Guyana GY
    Haiti HT
    Heard Island and McDonald Islands HM
    Holy See (Vatican City State) VA
    Honduras HN
    Hong Kong HK
    Hungary HU
    Iceland IS
    India IN
    Indonesia ID
    Iran, Islamic Republic of IR
    Iraq IQ
    Ireland IE
    Isle of Man IM
    Israel IL
    Italy IT
    Jamaica JM
    Japan JP
    Jersey JE
    Jordan JO
    Kazakhstan KZ
    Kenya KE
    Kiribati KI
    Korea, Democratic People's Republic of KP
    Korea, Republic of KR
    Kuwait KW
    Kyrgyzstan KG
    Lao People's Democratic Republic LA
    Latvia LV
    Lebanon LB
    Lesotho LS
    Liberia LR
    Libya LY
    Liechtenstein LI
    Lithuania LT
    Luxembourg LU
    Macao MO
    Macedonia, the former Yugoslav Republic of MK
    Madagascar MG
    Malawi MW
    Malaysia MY
    Maldives MV
    Mali ML
    Malta MT
    Marshall Islands MH
    Martinique MQ
    Mauritania MR
    Mauritius MU
    Mayotte YT
    Mexico MX
    Micronesia, Federated States of FM
    Moldova, Republic of MD
    Monaco MC
    Mongolia MN
    Montenegro ME
    Montserrat MS
    Morocco MA
    Mozambique MZ
    Myanmar MM
    Namibia NA
    Nauru NR
    Nepal NP
    Netherlands NL
    New Caledonia NC
    New Zealand NZ
    Nicaragua NI
    Niger NE
    Nigeria NG
    Niue NU
    Norfolk Island NF
    Northern Mariana Islands MP
    Norway NO
    Oman OM
    Pakistan PK
    Palau PW
    Palestine, State of PS
    Panama PA
    Papua New Guinea PG
    Paraguay PY
    Peru PE
    Philippines PH
    Pitcairn PN
    Poland PL
    Portugal PT
    Puerto Rico PR
    Qatar QA
    Reunion RE
    Romania RO
    Russian Federation RU
    Rwanda RW
    Saint Barthelemy BL
    Saint Helena, Ascension and Tristan da Cunha SH
    Saint Kitts and Nevis KN
    Saint Lucia LC
    Saint Martin (French part) MF
    Saint Pierre and Miquelon PM
    Saint Vincent and the Grenadines VC
    Samoa WS
    San Marino SM
    Sao Tome and Principe ST
    Saudi Arabia SA
    Senegal SN
    Serbia RS
    Seychelles SC
    Sierra Leone SL
    Singapore SG
    Sint Maarten (Dutch part) SX
    Slovakia SK
    Slovenia SI
    Solomon Islands SB
    Somalia SO
    South Africa ZA
    South Georgia and the South Sandwich Islands GS
    South Sudan SS
    Spain ES
    Sri Lanka LK
    Sudan SD
    Suriname SR
    Svalbard and Jan Mayen SJ
    Swaziland SZ
    Sweden SE
    Switzerland CH
    Syrian Arab Republic SY
    Taiwan, Province of China TW
    Tajikistan TJ
    Tanzania, United Republic of TZ
    Thailand TH
    Timor-Leste TL
    Togo TG
    Tokelau TK
    Tonga TO
    Trinidad and Tobago TT
    Tunisia TN
    Turkey TR
    Turkmenistan TM
    Turks and Caicos Islands TC
    Tuvalu TV
    Uganda UG
    Ukraine UA
    United Arab Emirates AE
    United Kingdom GB
    United States US
    United States Minor Outlying Islands UM
    Uruguay UY
    Uzbekistan UZ
    Vanuatu VU
    Venezuela, Bolivarian Republic of VE
    Viet Nam VN
    Virgin Islands, British VG
    Virgin Islands, U.S. VI
    Wallis and Futuna WF
    Western Sahara EH
    Yemen YE
    Zambia ZM
    Zimbabwe ZW


    In the Licenses list, select the Microsoft 365 licenses that you want to be assigned to new users.

    To customize which Microsoft 365 services will be enabled when a license is assigned to a user, select the Customize services checkbox.

    If this checkbox is not set, the default settings configured for the Microsoft 365 tenant associated with a user will be applied. For details, see Register Microsoft 365 tenant.

  5. To assign specific Microsoft 365 licenses only if certain conditions are met, you need to add an Activate or modify Microsoft 365 account action to a separate action set, and set the conditions there.

    • Click Add new action set.

    • To assign a condition to the new set, right-click it and then click Add Condition in the context menu.

    • In the Add Condition dialog, select the condition type and configure the condition parameters.

      Click OK.

    • To add an action to the set, right-click it and then click Add Action in the context menu.

    • In the Add Action dialog, select Activate or modify Microsoft 365 account.

    • In the Action Parameters section, select Modify Properties and click Edit.

    • Enable both checkboxes for the Microsoft 365 licenses that you want to be assigned to users.

      An enabled left checkbox means the license state will be modified for the user. The right checkbox determines the new license state: checked – assign the license; unchecked – revoke the license.

      To customize which Microsoft 365 services will be enabled when a license is assigned to a user, enable the Customize services checkbox.

      If the checkbox is not set, the settings configured for the Microsoft 365 tenant associated with a user will be applied. For details, see Register Microsoft 365 tenant.

    • Click OK two times.

  6. Click Save changes.

  7. You can configure Adaxes to automatically assign and revoke Microsoft 365 licenses when a user account is updated, added or removed from groups, moved to another organizational unit, etc.

    For example, if the Job Title property of a user account is changed, Adaxes can automatically revoke the Microsoft 365 licenses associated with the old job title, and assign the licenses that correspond to the new job title. To ensure that all users have the correct Microsoft 365 licenses, you can use a scheduled task to maintain license compliance.

    To share the license assignment rules between different business rules and scheduled tasks, create a custom command that will contain all the necessary actions and conditions, and then execute the command in business rules and scheduled tasks.

    Here is an example of a custom command that assigns and revokes licenses based on the user's job title.

    To execute a custom command, add an Execute a Custom Command action to your business rules and scheduled tasks.

    Deprovisioning Microsoft 365 accounts

    To revoke Microsoft 365 licenses when an employee leaves, you can use a built-in custom command, Deprovision. By default, it revokes all licenses and deactivates the user's account in Microsoft 365.

    For information on how to configure the custom command, see Configure user deprovisioning.

See also