Find the forms people actually use
Before a colleague changes role, ask which forms they maintain for the business. Our suggested starting point is one active process: a booking request, equipment request or customer survey. Record who receives the answers and who can explain what happens next. Avoid treating a working submission link as proof that the handover is complete.
Microsoft documents moving an owned form to a group, giving its members ownership. The person moving it must own the form and belong to the destination group. Our recommendation is to agree that destination with the process owner before making a change; membership should suit the information being collected.
Choose the destination deliberately
Microsoft says a group cannot currently transfer a form to another group. Check the intended home before proceeding rather than treating a move as an experiment. If the creator has already left, ask your Microsoft 365 administrator to review the separate supported transfer process; do not share the former employee’s credentials.
For a fictional maintenance business, an office coordinator maintains an equipment-request form. The service manager agrees which colleagues should operate the process and reviews the proposed group membership. They list the places the submission link appears, including the staff handbook, so those entry points can be checked during handover. This is an illustrative workflow, not a customer case.
Check the response workflow
Use a harmless, clearly labelled test submission through the approved process. Ask the new responsible colleague to find it and explain the next action without help from the creator. Where the process includes a notification or another workflow, test that step too instead of assuming it follows an ownership change.
Microsoft warns that moving the group form’s Excel response workbook to another location breaks synchronisation of new responses. Keep the workbook location within the handover check. Do not reorganise the files simply to make a folder look tidier without reviewing the documented behaviour.
Close the handover with evidence
Keep a brief record of the responsible team, approved destination, tested entry points and test result. Give any unresolved step an owner and a date. A form that accepts a request but leaves nobody responsible for acting on it should remain an open operational issue.
Review Microsoft’s current guidance before the move and ask the administrator to check account-lifecycle implications for existing links. This briefing is a planning aid, not a complete tenant-specific migration procedure. The useful outcome is a colleague who can demonstrate the process from a submitted request to its next action, with access appropriate to the business purpose.
Sources
Practical suggestions in this article are editorial recommendations. The source supports the guidance attributed to it.
- Microsoft Support · Move a form to a group ↗
Checked 13 October 2026
Something needs correcting?
Get in touch to explain which claim needs attention and share the supporting source.