No. When the replicas are in this state, it is still possible to logon and use the normal access request workflow. However, password checks and changes will not occur.
If "Change password after check-in" has been selected on the Access Request Policy, after a password release, further releases for the same account will fail with the "You cannot access this account while another request is pending password reset (90010)" error. In order for a user to access the account, an administrator would need to click on the "Pending Password Reset" in the Dashboard and select Close Request
Alternatively, the access policy could be changed with any of the following (note, these changes must be performed prior to the primary outage)
- Enable Emergency Access so a password reset does not need to occur
- Enable Allow simultaneous access on the Access Request Policy
- Remove the "Change password after check-in"
Enhancement request 226369 (Allow for Password reset when Primary offline and functionality when cluster has ReplicaWithQuorm) has been raised has been submitted to Development for consideration in a future release of the product