Forum Discussion
Multiple option select in my access portal entra
Subject: Guidance Required on Multiple Selection Functionality in Microsoft Entra Access Packages
Dear Microsoft Entra Team,
I am seeking guidance regarding the multiple selection functionality for requestor information questions in Microsoft Entra ID Governance Access Packages.
We have configured a multiple-choice question in an Access Package and updated the isMultipleSelectionAllowed property to true using the Microsoft Graph API. When we retrieve the assignment policy through a GET request, the property correctly returns true. However, in the My Access Portal, selecting a new option replaces the previously selected option instead of allowing multiple selections.
Could you please help clarify the following:
Is multiple selection for a single multiple-choice question officially supported in the My Access Portal? If so, is any additional configuration required beyond setting isMultipleSelectionAllowed to true through Microsoft Graph API?
If the My Access Portal does not currently support this behavior, what would be the recommended and supported approach to enable multiple selections for a single question without creating separate Access Packages for each option?
Although we could potentially use individual Yes/No questions, this may not be a scalable solution when users need to choose from 20+ roles. Managing and presenting a large number of separate questions could negatively impact usability and the overall request experience. We would be grateful if you could advise on any supported approach that allows multiple role selections within a single request form.
If multiple selections are supported and submitted through My Access, how can the selected responses be extracted and processed within an Azure Logic App?
Are there any alternative approaches within Microsoft Entra ID Governance to achieve this functionality other than Power Apps? While Power Apps could potentially address the requirement, we are concerned that it may bypass or reduce some of the existing governance and approval capabilities provided by Access Packages. We would appreciate your recommendations for achieving this requirement using supported Microsoft Entra capabilities.
We would greatly appreciate your technical guidance and recommendations on this matter.
Thank you for your time and assistance.
Kind Regards,
Likhith
2 Replies
- SelinaKnowIron Contributor
I'd test one new access package policy with a two-option question and isMultipleSelectionAllowed set through Graph, then submit it in My Access and inspect the assignment request's answers. That separates a portal rendering issue from a stored-answer issue. For 20+ roles, keep approval in Entra access packages and send Microsoft the policy JSON plus a My Access recording; I wouldn't build a Logic App around a selection the portal never submits.
- AmezingtechsataraIron Contributor
You're reading the Graph side correctly. Per Microsoft Graph's accessPackageMultipleChoiceQuestion documentation, isMultipleSelectionAllowed means exactly what it says — whether the requestor can select multiple choices as their answer — so a GET returning true means the policy is stored the way you intended. That doesn't by itself prove My Access will render it as checkboxes, and the behaviour you're seeing, a new choice replacing the last one, is what a single-select control does.
Two things are worth ruling out before treating it as a portal gap. First, make sure the policy you updated is the one the user is actually requesting through. An access package can have more than one assignment policy, and the question lives on the policy, so update the wrong one and the request flow won't change. Second, test it as a brand-new request, not by editing or reopening an existing one, and check what lands in the admin centre afterwards — the answers on a submitted request are where you'd see whether more than one choice was ever recorded.
If a fresh request on the right policy still replaces the choice, I'd raise that with Microsoft support as a My Access rendering issue, with the policy ID, the question ID and the GET response you already have. For the 20-plus roles in the meantime, the workable approach inside Entra ID Governance is usually to let the request itself stay simple and move the role detail somewhere it can hold a list — a Text question asking the requestor to list the roles, with the approver checking it, or splitting the roles across access packages in the same catalog so a user requests the packages they need, rather than trying to force 20 Yes/No questions into one form.