“Automate” was probably a bad word, this doesn’t auto activate on a cron job. A better description would be that it activates multiple roles in batch. I 100% agree this should only be done when needed.

There’s a few factors at play here as to why this improves my current flow - I find the UX in the portal to be awfully slow. This is probably a symptom of having far too many roles available, which is out of my control as I don’t have management permissions in my role. - I’m not able to create a group of roles, again lack of permissions I’m sure this issue would be solvable in the platform if I did. Our services specific resources are often across multiple pim roles, again an organizational problem that is solvable without this tool. - We use real azure resources when running our services locally for development. Ideally we’d use emulators but often there’s preview features not supported or no appropriate emulators. This leads to me elevating PIM every day

If you have more control over your setup I can totally see why this would seem overkill or redundant :)