M365 Employee Onboarding
Triggers on an HR request to concurrently provision a new hire's M365 workspace and send a personalized welcome email.
What it does
You get a fully ready digital workspace with your SharePoint lists, OneDrive folders, and Teams channel set up instantly when HR requests your onboarding. A personalized welcome email is sent to you while the system handles any setup errors so nothing stops your access.
Step by step
- Configure the trigger to listen for specific keywords in Teams messages or Outlook emails from HR.
- Set up parallel branches to execute SharePoint list creation, OneDrive folder generation, and Teams channel setup simultaneously.
- Implement a merge node with 'Continue on Fail' logic to ensure partial failures do not halt the entire workflow.
- Format the final output as a Microsoft Teams Adaptive Card to display the provisioning status to the user.
Where the LLM does the work
- Generate a personalized welcome email body that incorporates the new hire's name, role, and start date using the Anthropic Chat Model.
- Determine appropriate default permissions or group memberships for the new employee based on their job title extracted from the HR data.
Watch out for
Tools that fit
The agent brief
You are helping me build the following AI agent workflow. ## Goal M365 Employee Onboarding: Triggers on an HR request to concurrently provision a new hire's M365 workspace and send a personalized welcome email. ## Specification - What it does: You get a fully ready digital workspace with your SharePoint lists, OneDrive folders, and Teams channel set up instantly when HR requests your onboarding. A personalized welcome email is sent to you while the system handles any setup errors so nothing stops your access. - Trigger: Triggered by an event (Event ยท on Teams mention or Outlook email) - Autonomy: Fully hands-off - Expected setup effort: a few focused days - Tools/services involved: - Microsoft SharePoint: Create HR master list entry - Microsoft OneDrive: Provision personal folder structure - Microsoft Teams: Create onboarding channel and status card - Microsoft Outlook: Send welcome email - Anthropic Chat Model: Draft personalized welcome message ## Known pitfalls, handle each one explicitly in your implementation 1. Teams channel creation can fail if a channel with the same name already exists so add a check to rename or skip conflicting channels. 2. OneDrive folder paths may exceed length limits for nested structures so validate and truncate path strings before provisioning. 3. Error handling must capture specific failure reasons per branch so the final Adaptive Card can report exactly which service failed. ## Reference implementation https://n8n.io/workflows/15628 (workflow template) Fetch and inspect this before building. If it matches my stack, adapt it; if not, rebuild the pattern with my tools. ## Process requirements 1. Before building: ask me which of the listed tools I actually use and what my platform is (n8n / Make / code / other). Do not assume. 2. Adapt the pattern to my answers; do not force the reference stack. 3. Address every pitfall above; tell me how you handled each. 4. Provide a test plan I can run before letting this touch real data. 5. Ask before any step that sends messages, modifies data, or spends money. Source: https://usecasesforagents.com/use-case/automate-m365-employee-onboarding/ via usecasesforagents.com
Frequently asked questions
Can I use a different Notes & Docs than Microsoft SharePoint?
Yes. Microsoft SharePoint is only the example notes & docs in this recipe. The same flow works with Figma, Google Docs, Google Slides and Notion. Swap the notes & docs connection and keep the rest of the setup as written.
Want this running in your business?
Who it's for
Built for Ops-IT teams who need one more recurring task off a human's plate.
HR and recruiting teams can lift this pattern directly into their own workflow.