1
For account login, we would like to use a velocity to assist in determining whether to challenge (require verification of SMS number in our scenario) a login attempt. The business requirement is: “Don’t [re]challenge a login attempt if the consumer has successfully completed an SMS challenge in the last 7 days”. This requirement seems tailor-made for a velocity-based rule; however, we can't currently create a velocity using results from AP status API calls, which we would need to record the outcome of the SMS challenge.
Account Login Status: /v1.0/observe/account/login/status/{UserId}
Account Creation Status: /v1.0/observe/account/create/status/{SignUpId}
"statusDetails": {
"statusType": "Approved",
"reasonType": "ChallengePassed",
"challengeType": "SMS",
"statusDate": "2022-12-30T14:12:28.3399685+00:00"
},
STATUS DETAILS
Completed
Administrator
Thank you for this valuable feedback. This use case can be addressed using cross-event velocities available in the product.
Please refer to the following link for more information: https://learn.microsoft.com/en-us/dynamics365/fraud-protection/velocities
Best regards,
DFP Team