How to limit virtual attributes retrieval?

Can you share the code you are using to populate these attributes (or a piece of it)?

There are ways to fetch attribute contents more quickly.

You can use grab client information and only load the Virtual Attributes when needed, or use a custom Control, as per this resource:

Title: HOW TO: Determine which Active Roles client is performing a modification using a custom script module
Solution: 284750
URL: https://support.oneidentity.com/kb/284750 

Well, this is a complex code, but idea is that the value of each property is queried through a GraphAPI web call towards Ms365, consuming milliseconds we cannot get rid of, unfortunately...

Hopefully you know that when configured correctly to communicate with M365, Active Roles also makes Graph calls to pull various attributes whenever you look at the properties of an object.  I would be concerned that your code may be duplicating some of this.  Have you compared the attributes that Active Roles pulls "natively" with those that you are pulling?

That's right, and indeed some are already there, so duplicates, but I also "build" some other values (for user-friendly display), so I unfortunately need most of these calls.

Thanks, this is a very interesting post.

That's nevertheless not enough for what I am trying to achieve, though, as I need to display these in all 3 clients (MMC, WI and PS).
The criteria I'm looking for would rather be something like "only when needed"...

Isn't there a way to detect if a given attribute will actually be displayed (or was explicitly requested)?

You can define your own Control associated with a web ui properties page or Wizard - I did this for one customer.  We decided to call the control "WebUIFormID". 

Your OnPostGet handler can check $Request.GetInControl("WebUIFormID" to see if the UI needs to do the manipulation of the attributes based on whether this Control is present and/or based on its value.

<*>  <*>  <*>

Another thought:

I know that this is different than your current architecture / approach,

Create a Sync Service job that would update stored versions of your "friendly" virtual attributes with information from your M365 tenant.  I see it working something like this:

Sync service job (runs daily(?) - or however often you want):

UserAttribute1 (from Cloud) ---> VATempUserAttribute1 (not stored)

Workflow detects change to VATempUserAttribute1, processes its contents and stores the "friendly" version in VAFriendlyAttribute1 (stored attribute)

That way you always have VAFriendlyAttribute1 on hand for the UI to read quickly.