Solutions
Make service requests clear from the start.
Publish request forms, decision owners and fulfillment evidence in one service workflow.
The work to improve
A catalog is useful when it explains what happens after someone clicks Request. Employees and operators need a shared view of the request, approval and result.
Each request keeps the catalog revision and answers reviewed for that run. A later policy change does not silently rewrite the original decision.
Operators can open Fulfillment to inspect the current state and the actions available to them. Requester feedback and service outcomes add another view of what happened after fulfillment.
What changes for your team
- Help eligible members find the right service.
- Keep the reviewed request and policy together.
- Make fulfillment ownership and evidence visible.
What you can explore in Vision
- Searchable catalog with required request fields
- Private revision-pinned service requests
- Manual evidence receipts and supported Entra access fulfillment
Questions worth asking
Who sees a new catalog request?
The request starts private to its requester and named reviewers and fulfillment owners, with current access controls applied.
Can the requester approve it?
No. The fulfillment approval requires an independent assigned reviewer.
Does manual completion prove an external action?
It records an assigned owner’s observed result and evidence reference; it is not independent provider verification.
Scope and availability
- ITSM Service requests must be licensed and enabled.
- Catalog execution is limited to supported fulfillment types and configured providers.