Managed Identity assignment limit

[mptherefore]

Bicep version
Bicep CLI version 0.33.13 (48521b9)

Describe the bug
There is a problem that as soon as you have more than 150 user assigned identities you cannot assign them to a VM or VMSS anymore using bicep. You receive the following error:
'Failed to perform resource identity operation. Status: 'BadRequest'. Response: '{"error":{"code":"BadRequest","message":"User Assigned Identities Number '151' Assign exceed limit '150' in one request."}}'.'.

To Reproduce
Steps to reproduce the behavior:

1. create more than 150 user assigned identities
2. assign those to a single VM or VMSS.

Additional context
We are using a very similar scenario like described in this article:
https://learn.microsoft.com/en-us/azure/role-based-access-control/conditions-custom-security-attributes-example
To achieve this we are using one user assigned managed identities per customer which has the custom security attribute set.
In our case we have a few additional user assigned identities that are needed e.g. for KeyVault extension to download a certificate and another one for Azure Monitoring Agent extension. Those obviously have to be assigned when creating the VM/VMSS.
How can we achieve this?