A resource role assignment has three parts: a principal, a role definition and a scope. Read all three.
A familiar role on the wrong subscription doesn't authorize the requested work, and a broad role can grant more than the task requires.
Control-plane actions and data actions also differ. Resource Reader can inspect management metadata without granting private blob reads. Choose the role that covers the approved action, then restrict its scope. The simulator checks the saved assignment. Production access can also depend on other assignments, deny rules and service restrictions, so this local result isn't an effective-access test against a live account.
Save the principal, role and exact approved scope.