Senior Microsoft 365 Messaging & Governance Engineer

We need to output only HTML fragment, with headings

for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate, navigation, EEO, etc. Must not include sections with placeholder like "commensurate with experience". The posting includes Salary: $125,000 - $140,000 per year. So we can have Pay section with that. Benefits? Not mentioned explicitly. There's "Why join us?" bullet points but those are more about role, not benefits. No explicit benefits like health insurance etc. So we should not create Benefits section unless posting actually states them. It does not list benefits. So omit Benefits. Schedule? Not mentioned. So omit Schedule. We need sections: About the role (maybe "A bit about us" and "Job Details" etc). Responsibilities (What You’ll Do). Requirements (What We’re Looking For). Qualifications (Preferred Qualifications). Skills maybe combine? But we can have Skills section if there is specific skill list. The posting includes many skill requirements; we could put them under Requirements or Skills. But we need to follow instruction: use headings for those categories if content exists. We can decide to have About the role, Responsibilities, Requirements, Qualifications, Skills, Pay. Ensure we don't create empty sections. We must preserve all substantive information; not invent or summarize away detail. So we need to include details from the posting. Let's parse content: - About the role / company: "A bit about us: We are a large, highly collaborative organization with a complex Microsoft 365 environment supporting teams and business units across the enterprise. Our technology organization is focused on building secure, scalable, and well-governed platforms that enable the business to collaborate effectively while protecting critical data. This is an opportunity to join a mature technology organization while helping shape an area that is still evolving. You will work across messaging, collaboration, cybersecurity, GRC, enterprise applications, and business teams to establish standards that can scale across a large organization." Also "Why join us?" bullet points: Build rather than simply maintain..., Stay technically engaged..., High visibility..., Complex enterprise environment..., Balance strategy and execution..., Opportunity to make an impact... These are more about role benefits but could be part of About the role or separate. We'll incorporate into About the role. - Responsibilities: "What You’ll Do" with subheadings: M365 Governance & Architecture, Automation & Reporting, Messaging & Collaboration Engineering, Business & Stakeholder Partnership. Under each bullet list. We need to output as

• for any list of duties/requirements/benefits. So we need to convert those bullet points into list items. We must preserve all substantive info; not summarize away detail. So we need to include each bullet point as a list item. Let's extract each bullet: Under M365 Governance & Architecture: - Help design, implement, and continuously mature the governance framework for Exchange Online and Microsoft Teams - Establish governance policies including naming conventions, provisioning workflows, ownership standards, and full lifecycle management - Define standards around the creation, ownership, archival, and deletion of mailboxes, distribution lists, Microsoft 365 Groups, and Teams - Configure and maintain retention policies, sensitivity labels, and Data Loss Prevention rules using Microsoft Purview - Develop governance standards for external sharing, guest access, and permissions within Microsoft Teams - Identify opportunities to reduce oversharing and data exposure while maintaining an effective user experience - Partner with GRC, cybersecurity, and other stakeholders to translate risk and compliance requirements into actionable M365 controls - Conduct access reviews and governance audits to identify policy drift and areas of risk - Help establish governance policies in areas where formal standards may not yet exist Automation & Reporting: - Develop automation using PowerShell, Microsoft Graph API, and Power Automate - Automate governance activities such as orphaned mailbox and Team cleanup, ownership certification, lifecycle management, and policy enforcement - Build and maintain reporting and dashboards using Power BI, Purview, or native Microsoft 365 reporting - Track governance adherence, compliance posture, licensing, and platform utilization - Evaluate new Microsoft 365 governance and compliance capabilities and determine their potential impact before broader rollout Messaging & Collaboration Engineering: - Administer and engineer Exchange Online environments - Support mail flow rules, connectors, distribution lists, shared mailboxes, and anti-spam and anti-phishing controls - Support Microsoft Teams architecture including meeting policies, channel structure, Teams applications, and related platform configuration - Troubleshoot complex platform-level issues - Monitor service health and support capacity and licensing planning - Partner with Microsoft support and internal technology teams when required Business & Stakeholder Partnership: - Work directly with business units to understand collaboration requirements and translate them into scalable governance standards - Explain the reasoning behind governance policies to both technical and non-technical stakeholders - Balance security, compliance, and risk requirements against business productivity and usability - Drive adoption of governance standards without creating unnecessary roadblocks for users - Create and maintain governance documentation, technical standards, runbooks, and training materials - Serve as an escalation point for governance-related incidents including oversharing, policy violations, and permissions issues Now Requirements: "What We’re Looking For" bullet list: - 7+ years of experience within Microsoft 365 governance, messaging, collaboration, administration, or engineering - Strong hands-on experience with Exchange Online and/or Microsoft Teams - Demonstrated ability to help design, architect, or significantly mature M365 governance standards rather than simply administer existing policies - Strong experience with Microsoft Purview, including: - Retention policies and labels - Data Loss Prevention - Sensitivity labels - Experience designing lifecycle management, naming standards, access controls, ownership models, and sharing governance for Microsoft 365 environments - Strong PowerShell experience within Microsoft 365 - Familiarity with Microsoft Graph API for automation and reporting - Understanding of Exchange Online mail flow and Microsoft Teams architecture - Familiarity with regulatory and compliance frameworks such as GDPR, HIPAA, SOC 2, ISO 27001, and NIST as they relate to messaging and collaboration - Experience with Microsoft 365 licensing and optimization - Strong documentation and analytical skills - Ability to translate technical and governance requirements into clear recommendations for business stakeholders - Strong communication skills and the ability to work across technical teams, security, compliance, and business groups We need to preserve sub-bullets under Strong experience with Microsoft Purview. Should we keep as nested list? Probably we can keep as
  • with inner
    . That's fine. Now Qualifications: "Preferred Qualifications" bullet list: - Microsoft certifications such as SC-400, MS-102, or MS-700 - Background supporting IT compliance, risk management, or audit initiatives - Experience supporting Microsoft 365 Copilot data readiness, including oversharing remediation and sensitivity-label coverage - Experience with Power Automate and Power BI - Exposure to ITIL or formal change management practices - Familiarity with Teams Phone or voice engineering, including direct routing, calling plans, or PSTN connectivity - Experience with messaging or collaboration migrations, including legacy Exchange, email platform, Teams, or Slack migrations Now Skills: Could be a separate section summarizing skills like PowerShell, Microsoft Graph API, etc. But we already have many skills in Requirements. Might be redundant. However instruction: Prefer a few substantive sections over many thin ones. Could combine Requirements and Qualifications into one? But headings are prescribed; we can include both if they have content. We'll include Requirements and Qualifications separate. Pay: Salary: $125,000 - $140,000 per year. Now About the role: We need to include the "A bit about us:" and "Why join us?" points. Also maybe "Job Details" paragraph: "We are looking for a Senior M365 Governance Engineer to help architect and own the governance framework across Microsoft 365 messaging and collaboration platforms, primarily Exchange Online and Microsoft Teams, while partnering with enterprise application teams supporting SharePoint and OneDrive. This is not a traditional governance-only position. We are looking for someone with a strong foundation in the Microsoft 365 and messaging space who understands the underlying technology well enough to help define practical, scalable governance policies. You will help establish and mature standards around lifecycle management, retention, data protection, external sharing, access, and policy enforcement. You will work closely with GRC, security, technology teams, and business stakeholders to translate governance and compliance requirements into technical controls that protect the organization without unnecessarily limiting productivity. Hands-on Exchange Online and Teams engineering is an important part of the role, but the larger goal is to ensure the environment is governed intentionally and policies are incorporated by design rather than as an afterthought." That's substantive; include in About the role. Now we must not include boilerplate like "Want to learn more about this role and Jobot? Click our Jobot logo and follow our LinkedIn page!" etc. Also remove "Job details: This Jobot Job is hosted by: Amanda Preston Are you a fit? Easy Apply now by clicking the "Easy Apply" button and sending us your resume." etc. Also remove "Interested in hearing more? Easy Apply now by clicking the "Easy Apply" button." and EEO etc. Now output HTML fragment with sections. Structure:

    About the role

    ... paragraphs ...

    Maybe we need to split into multiple paragraphs for readability but okay. Then

    Responsibilities

    • ... (maybe group by subheadings? The instruction says use
      • for any list of duties/requirements/benefits. It didn't say we need subheadings inside list. Could keep as flat list. But we could also include subheadings as

        ? Not allowed; only headings specified are

        for section headings. We could still include

        but not specified; better to avoid extra headings. We'll just list all duties as flat list items. But we have many items; we can keep them as is. Similarly for Requirements:

        Requirements

        ...
        Qualifications:

        Qualifications

        ...
        Skills: maybe not needed; but we could combine some skills into Requirements. However we have many skill-like items already in Requirements. Could we create Skills section for things like PowerShell, Microsoft Graph API, etc? But they'd be duplicates. Better to omit Skills section to avoid thin section. The instruction: Prefer a few substantive sections over many thin ones. So we can omit Skills. Pay:

        Pay

        $125,000 - $140,000 per year

        Now ensure we didn't miss any substantive info: The "Why join us?" bullet points we haven't included yet. Should we include them in About the role? Yes we can incorporate them as part of About the role paragraph or as a list. Since they are substantive, we need to preserve them. We could add them as a
        under About the role? But About the role is supposed to be prose; we could add a
        inside but that's okay. However instruction: Use
        • for any list of duties/requirements/benefits, and

          for prose. The "Why join us?" points are more like benefits/reasons to join; could be considered benefits but we don't have Benefits section. We could treat them as a list under About the role as

          . That would be a list, so we should use
          • . That's fine. Thus About the role could have a

            for the "A bit about us:" paragraph and the Job Details paragraph, then a <