[GH-ISSUE #1067] [Feature Request]: #564

Closed
opened 2026-03-02 12:43:18 +03:00 by kerem · 2 comments
Owner

Originally created by @binary-ops on GitHub (Aug 15, 2022).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1067

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

New standard to include additional context and number matching to MFA

PowerShell commands you would normally use to achieve above request

Additional Context: https://docs.microsoft.com/en-us/azure/active-directory/authentication/how-to-mfa-additional-context

//Retrieve your existing policy via a GET.
//Leverage the Response body to create the Request body section. Then update the Request body similar to the Request body as shown below.
//Change the Query to PATCH and Run query

{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity",
"@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration",
"id": "MicrosoftAuthenticator",
"state": "enabled",
"includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets",
"includeTargets": [
{
"targetType": "group",
"id": "all_users",
"authenticationMode": "any",
"displayAppInformationRequiredState": "enabled",
"numberMatchingRequiredState": "enabled"
}
]
}

MFA number Matching: https://docs.microsoft.com/en-us/azure/active-directory/authentication/how-to-mfa-number-match

//Retrieve your existing policy via a GET.
//Leverage the Response body to create the Request body section. Then update the Request body similar to the Request body as shown below.
//Change the Query to PATCH and Run query

{
"@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity",
"@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration",
"id": "MicrosoftAuthenticator",
"state": "enabled",
"includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets",
"includeTargets": [
{
"targetType": "group",
"id": "all_users",
"authenticationMode": "any",
"displayAppInformationRequiredState": "enabled",
"numberMatchingRequiredState": "enabled"
}
]
}

Originally created by @binary-ops on GitHub (Aug 15, 2022). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/1067 ### Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. New standard to include additional context and number matching to MFA ### PowerShell commands you would normally use to achieve above request Additional Context: https://docs.microsoft.com/en-us/azure/active-directory/authentication/how-to-mfa-additional-context //Retrieve your existing policy via a GET. //Leverage the Response body to create the Request body section. Then update the Request body similar to the Request body as shown below. //Change the Query to PATCH and Run query { "@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity", "@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration", "id": "MicrosoftAuthenticator", "state": "enabled", "includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets", "includeTargets": [ { "targetType": "group", "id": "all_users", "authenticationMode": "any", "displayAppInformationRequiredState": "enabled", "numberMatchingRequiredState": "enabled" } ] } MFA number Matching: https://docs.microsoft.com/en-us/azure/active-directory/authentication/how-to-mfa-number-match //Retrieve your existing policy via a GET. //Leverage the Response body to create the Request body section. Then update the Request body similar to the Request body as shown below. //Change the Query to PATCH and Run query { "@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodConfigurations/$entity", "@odata.type": "#microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration", "id": "MicrosoftAuthenticator", "state": "enabled", "includeTargets@odata.context": "https://graph.microsoft.com/beta/$metadata#authenticationMethodsPolicy/authenticationMethodConfigurations('MicrosoftAuthenticator')/microsoft.graph.microsoftAuthenticatorAuthenticationMethodConfiguration/includeTargets", "includeTargets": [ { "targetType": "group", "id": "all_users", "authenticationMode": "any", "displayAppInformationRequiredState": "enabled", "numberMatchingRequiredState": "enabled" } ] }
kerem 2026-03-02 12:43:18 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (Aug 15, 2022):

Thank you for creating a feature request! feature requests are prioritized by our direct contributors. Your current priority is set to "No Priority". If you are a sponsor you can request an upgrade of priority, If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://kelvintegelaar.github.io/CIPP/GettingStarted/Contributions.html. Contributors to the CIPP project reserve the right to close feature requests at will.

If your feature request is not picked up in 2 week by a contributor it will be closed.

If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".

<!-- gh-comment-id:1215495554 --> @github-actions[bot] commented on GitHub (Aug 15, 2022): Thank you for creating a feature request! feature requests are prioritized by our direct contributors. Your current priority is set to "No Priority". If you are a sponsor you can request an upgrade of priority, If you want this feature to be integrated you can always do this yourself by checking out our contributions guide at https://kelvintegelaar.github.io/CIPP/GettingStarted/Contributions.html. Contributors to the CIPP project reserve the right to close feature requests at will. If your feature request is not picked up in 2 week by a contributor it will be closed. If you'd like this feature request to be assigned to you, please comment "I would like to work on this please!".
Author
Owner

@KelvinTegelaar commented on GitHub (Aug 15, 2022):

closed, already exists

<!-- gh-comment-id:1215497947 --> @KelvinTegelaar commented on GitHub (Aug 15, 2022): closed, already exists
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/CIPP#564
No description provided.