How attribute policies work on Modify action

Summary: Cayosoft Administrator has granular control over how attribute data is presented or modified through the use of attribute policies, applied to the desired scope (Administrative Units). This article will describe how the attribute police work on the Modify action. Learn more about attribute policies in: Attribute policies .

Applies to: Cayosoft Administrator 5.1.0 or later

When configuring an attribute policy, you define how attribute data should be presented on an object's form through the corresponding controls. However, when applying this policy to a Modify action such as updating Microsoft 365 Licenses or User Properties keep in mind that the object already exists and has predefined attribute values.

All actions that modify existing object properties are considered Modify actions. These include:

• User Properties

• Mail Properties

• Office 365 License

• And other similar actions

When performing a Modify action in the Web Portal, the form always displays the object's current attribute values.

Impact of Attribute Policies on Modify actions

Because the form pre-fills attributes with their current values, default values from attribute policies do not apply in Modify actions. This differs from actions like New User creation, where default values are automatically assigned.

However, other attribute policy settings do apply, including:

• Possible values

• Minimum and maximum values

• Label modifications

• Read-only and Hide flags

These settings affect how the attribute is presented but do not override existing values.

Conflict handling

If an attribute policy enforces a value that conflicts with the current attribute value, an error message will appear next to the property when attempting to update the object.

For more details on Attribute Policies and their functionality, refer to the Cayosoft Administrator Service documentation: Attribute policies .

How the attribute policy works on Office 365 License action

A user doesn't have the license defined in the policy

When configuring the attribute policy for the Microsoft 365 License action, one of the attributes you could specify is Licenses. On the Attribute Policy setting for Licenses, you select which licenses or license options should be applied to a user, which should be read-only or hidden:

If you connect to the Web Portal, find a user that doesn't have this license assigned, and click the Office 365 Licenses action for this user, you will see the licenses that are marked as <Not Set> and Read-only, hidden plans, and options won't be available on the form:

If you select the E3 license plan, it would have only the options defined in the policy - Teams and Exchange online, To-Do option will be hidden:

A user has the license defined in the policy

If a user already has the license defined in the policy - E3 Plan and all its options, and the attribute policy is defined as on the picture above, then you will see all the licenses and options currently assigned to this user:

If you uncheck the E3 Plan and check it again, the license and its options defined in the policy will be applied. But you still need to uncheck the To-Do option manually and save changes to exclude it from the options list.

If a user has the license plan assigned but this license plan is either hidden by the policy or just made read-only or read-only (including options), this license plan will be displayed on Web Portal as read-only.

TIP: For Office 365 license assignment please use the following Cayosoft automation rules:

• Microsoft 365 Users | Enforce License

• Office 365 Groups | Enforce Licenses

For more information about license plans visibility in the Web Portal, review the following article:  Attribute policies .