New Employee Welcome Email with Manager Info

Overview

This flow watches for new user accounts created in Microsoft 365 (via Azure AD/Entra ID) and, for each new hire, enriches the welcome experience by pulling the user's manager and department from the directory before sending a personalized welcome email from HR. The result is a hands-off onboarding touchpoint that arrives the moment IT provisions the account, with org context (department, job title, manager name and email) already baked in.

It is intentionally simple so HR or IT can adapt it without rebuilding the trigger: change the subject, swap the email body, route to a shared mailbox, or add a CC to the manager. Tenant-specific values (sender mailbox, HR signature, optional CC) are exposed as environment variables so deploying into a new tenant only requires updating defaults — no flow edits required.

Use Case

Most onboarding workflows fire from an HRIS export or a manual ticket, which means the welcome email arrives hours or days after the account is actually usable. This flow closes that gap by reacting to Azure AD directly — the moment the new user record exists, the welcome email goes out with manager info already included, so the new hire has a friendly first message in their inbox before they even sign in.

It is the lightest-weight piece of a larger onboarding stack and pairs well with provisioning, training-assignment, and Teams-introduction flows.

The flow is ideal for teams that:

• HR teams who want new hires to get a warm, branded welcome email automatically
• IT admins who provision accounts in Azure AD/Entra and want HR notified without a manual handoff
• Small and mid-size orgs without a full HRIS-to-Power-Automate integration
• Teams piloting Power Automate that need a low-risk, high-visibility first flow

Flow Architecture

Environment Variables

Connectors & Connections

Note — All connections are referenced as solution connection references; the flow is portable between environments as long as a connection is mapped at import time.

Customization Guide

Almost every realistic variant of this flow can be implemented by changing environment variable values. A few cases require small edits inside the flow definition — those are called out explicitly below.

Brand the email body

Replace the placeholder welcome body with your org's onboarding copy. Use the dynamic content for DisplayName, Department, JobTitle, and Manager.DisplayName so personalization survives the swap.

Route via a shared HR mailbox

Set flowlibs_WelcomeSenderMailbox to a shared mailbox (e.g. hr@yourcompany.com) and ensure the connection account has Send-As permission. This keeps replies in the HR inbox rather than an individual's mailbox.

Suppress the manager CC

Flip flowlibs_CcManagerOnWelcome to No to send the welcome email only to the new hire — useful in tenants where managers prefer a separate notification flow.

Filter by department or location

Add a condition immediately after Get user profile to short-circuit when the user's Department or UsageLocation does not match the values you want to welcome (e.g. exclude service accounts or contractors).

Key Expressions

The flow is intentionally light on Power Fx / WDL gymnastics — the heaviest expressions are the branch-name concatenation and the approval outcome check. They are listed below in the order they appear in the flow.

and(not(equals(outputs('Get_user_profile_(V2)')?['body/department'], 'Service')), not(startsWith(triggerOutputs()?['body/userPrincipalName'], 'svc_')))

not(empty(outputs('Get_manager_(V2)')?['body/mail']))

concat('Hi ', outputs('Get_user_profile_(V2)')?['body/givenName'], ', welcome to your-org!')