Use cases
Start with the job in front of you. The inbox, the file share, or the spreadsheet that is still holding the process together.
Start with the job in front of you. The inbox, the file share, or the spreadsheet that is still holding the process together.
A purchase request lives in email. Leave lives in a spreadsheet. Vendor onboarding lives in a shared folder. Each one has a different form, a different approver, and no shared record of who decided what.
Approval Management Hub keeps those requests in the SharePoint site the team already uses. A designer publishes the form and the stages. A requester submits from Teams or SharePoint. The approver opens the queue, approves, rejects, or places the request on hold, and can name a delegate for an absence.
Closed requests carry a closed date, so cycle time is the time from submit to close. Open work stays out of that average. The audit log keeps the person, the action, and the time. Budgets show the pool, the amount spent, and the amount remaining for the requests that draw against them.
When the only queue is an inbox, the person who asked sends a second email to ask what happened. The agent who could answer is looking at a different thread.
Help Desk 365 and Service Desk Hub give that request a record: who submitted it, who owns it, and whether it is open, in progress, resolved, or closed. The requester checks the status in Teams or SharePoint instead of asking again.
Use Help Desk 365 when the job is a shared request list, a board, and analytics. Use Service Desk Hub when the job also needs a knowledge base, queues, and a help center for the people who submit work.
Posting a PDF on the intranet records that the file exists. It does not record who opened it, who acknowledged it, or which version they saw.
Policy & Attestation publishes a version, assigns it to employees and managers, and keeps the acknowledgment. A review can export who is done and who is still waiting. The policy content and the responses stay in the SharePoint tenant.
This is the job when legal, security, or HR needs a list of names, not a link in a newsletter.
A branded home for news, policies, and documents, with navigation a new hire can explain on day one. It stays in the tenant you already pay for.
Move what people still use into libraries they can search. Permissions map to groups, and the old clutter stays behind.
Screens for the real task, with validation and roles, while the rows stay in SharePoint or Dataverse. A flow covers the handoff when email is still the approval path.
A directory and org chart drawn from the people already in Microsoft 365, so the answer is a search instead of a message.
Requisitions, candidates, interviews, and offers in one desk, with the scorecards and the audit trail beside the pipeline.
Tasks, policies, and training for the person joining, and a view for the manager who has to know what is still open.
A register of assets, who has them, and when they are due back, with the assignment history kept on the site.
A sourcing event, sealed supplier responses, a scored evaluation, and an award recommendation in one workspace.
Pre-registration, check-in, and a record of who is on site, including the list you need if the building has to be cleared.
A rated risk, an owner, a treatment, and a review date, so the register is a list people update instead of a deck from last quarter.
A weekly timesheet, an approval, and, when you bill clients, rates and invoices drawn from the time that was approved.
See who can open a site, change access in bulk, and export the picture before and after the change.
If an installed app covers it, we point you there. If the process is specific to you, the proposal says what the build includes.