Microsoft 365 Security Manager
Deloitte · Hermitage, TN · 1 mo ago
Hybrid$135k–$265k/yrFull-time
We need to produce HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "Our Deloitte Cyber team understands the unique challenges and opportunities businesses face in cybersecurity. Join our team to deliver powerful solutions to help our clients navigate the ever-changing threat landscape. Through powerful solutions and managed services that simplify complexity, we enable our clients to operate with resilience, grow with confidence, and proactively manage to secure success."
- Then "Work you'll do" with bullet list of duties (actually paragraphs). We'll need to extract responsibilities.
- Then "The team" paragraph.
- Then "Recruiting for this role ends on 12/31/2026." (metadata, maybe include in short p).
- Then "Required Qualifications:" with bullet list.
- Then "Additional Requirements:" bullet.
- Then "Preferred Qualifications:" bullet.
- Then wage range paragraph.
- Then "You may also be eligible to participate in a discretionary annual incentive program..."
We need sections: About the role (intro), Responsibilities (work you'll do), Requirements (maybe combine required qualifications?), Qualifications (maybe preferred?), Skills (maybe technologies?), Benefits (maybe incentive program?), Pay (wage range), Schedule (travel requirement? maybe schedule not given; travel up to 50% could be schedule? Not exactly schedule. Could treat as "Travel" but schedule not present. We should not create Schedule unless posting actually states schedule. It does not mention schedule like full-time/part-time, hours. So we should omit Schedule.
Benefits: we have discretionary annual incentive program. That's a benefit. Also maybe mention limited sponsorship? That's not benefit. So we can include Benefits section with that.
Pay: wage range given.
Skills: maybe list of technologies? Could be under Skills. But we have Required Qualifications and Preferred Qualifications sections. Could combine them into Requirements and Qualifications. The instruction: Use headings for sections e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content.
We have:
- About the role: intro paragraph.
- Responsibilities: "Work you'll do" bullet list.
- Requirements: Required Qualifications (maybe also Additional Requirements). Could be Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe list of specific technologies (like Purview, Intune, etc.) but those are already in responsibilities and qualifications. Could still create Skills section summarizing technical skills: Microsoft 365 security stack, etc. But we must not invent or summarize away detail; we must preserve all substantive info. If we create Skills section, we need to include the specific technologies listed. Could extract from responsibilities and qualifications. However we must not duplicate content? It's okay to repeat? Probably better to keep responsibilities as is, and not create Skills unless we have explicit skills list. The posting does not have a separate "Skills" heading; but we can create one if we have substantive content: we could list the specific Microsoft technologies mentioned as required experience. That is substantive. But we must not invent; we can extract from Required Qualifications and Preferred Qualifications. That seems okay.
- Benefits: discretionary annual incentive program.
- Pay: wage range.
- Schedule: not present, omit.
We also have "Recruiting for this role ends on 12/31/2026." Could be placed in a short p under About the role or separate metadata. Could be a short p after About the role.
We must not include boilerplate like "Our Deloitte Cyber team..." is okay.
We must not include navigation/legal/EEO etc. Not present.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
Structure:
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections if posting has real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate, navigation, legal, EEO, etc. Must preserve all substantive info.
We need to parse the posting.
Content:
- Intro paragraph: "Our Deloitte Cyber team understands the unique challenges and opportunities businesses face in cybersecurity. Join our team to deliver powerful solutions to help our clients navigate the ever-changing threat landscape. Through powerful solutions and managed services that simplify complexity, we enable our clients to operate with resilience, grow with confidence, and proactively manage to secure success."
- Then "Work you'll do" with bullet list of duties (actually paragraphs). We'll need to extract responsibilities.
- Then "The team" paragraph.
- Then "Recruiting for this role ends on 12/31/2026." (metadata, maybe include in short p).
- Then "Required Qualifications:" with bullet list.
- Then "Additional Requirements:" bullet.
- Then "Preferred Qualifications:" bullet.
- Then wage range paragraph.
- Then "You may also be eligible to participate in a discretionary annual incentive program..."
We need sections: About the role (intro), Responsibilities (work you'll do), Requirements (maybe combine required qualifications?), Qualifications (maybe preferred?), Skills (maybe technologies?), Benefits (maybe incentive program?), Pay (wage range), Schedule (travel requirement? maybe schedule not given; travel up to 50% could be schedule? Not exactly schedule. Could treat as "Travel" but schedule not present. We should not create Schedule unless posting actually states schedule. It does not mention schedule like full-time/part-time, hours. So we should omit Schedule.
Benefits: we have discretionary annual incentive program. That's a benefit. Also maybe mention limited sponsorship? That's not benefit. So we can include Benefits section with that.
Pay: wage range given.
Skills: maybe list of technologies? Could be under Skills. But we have Required Qualifications and Preferred Qualifications sections. Could combine them into Requirements and Qualifications. The instruction: Use headings for sections e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to decide which sections to include based on content.
We have:
- About the role: intro paragraph.
- Responsibilities: "Work you'll do" bullet list.
- Requirements: Required Qualifications (maybe also Additional Requirements). Could be Requirements.
- Qualifications: Preferred Qualifications.
- Skills: maybe list of specific technologies (like Purview, Intune, etc.) but those are already in responsibilities and qualifications. Could still create Skills section summarizing technical skills: Microsoft 365 security stack, etc. But we must not invent or summarize away detail; we must preserve all substantive info. If we create Skills section, we need to include the specific technologies listed. Could extract from responsibilities and qualifications. However we must not duplicate content? It's okay to repeat? Probably better to keep responsibilities as is, and not create Skills unless we have explicit skills list. The posting does not have a separate "Skills" heading; but we can create one if we have substantive content: we could list the specific Microsoft technologies mentioned as required experience. That is substantive. But we must not invent; we can extract from Required Qualifications and Preferred Qualifications. That seems okay.
- Benefits: discretionary annual incentive program.
- Pay: wage range.
- Schedule: not present, omit.
We also have "Recruiting for this role ends on 12/31/2026." Could be placed in a short p under About the role or separate metadata. Could be a short p after About the role.
We must not include boilerplate like "Our Deloitte Cyber team..." is okay.
We must not include navigation/legal/EEO etc. Not present.
We must not repeat job title as heading.
We must not put Job ID/requisition numbers as headings.
We must output only HTML fragment.
Let's craft.
Structure:
About the role
Our Deloitte Cyber team understands the unique challenges and opportunities businesses face in cybersecurity. Join our team to deliver powerful solutions to help our clients navigate the ever-changing threat landscape. Through powerful solutions and managed services that simplify complexity, we enable our clients to operate with resilience, grow with confidence, and proactively manage to secure success.
Recruiting for this role ends on 12/31/2026.
Responsibilities
- Lead projects and/or function as project lead architect with the following Microsoft technologies: Purview, Intune, Sentinel, Entra ID, Defender for Office, Defender for Endpoints and Servers, Defender for Vulnerabilities, Defender for Cloud Apps, Defender XDR and SCCM
- Assist in business development activities such as defining scope of services, building resource estimates and related pricing, packaging proposals and supporting the delivery of the proposal to the client for M365 security services.
- Lead the delivery of cloud security analysis, recommendations and configurations of prospective clients' Microsoft Entra ID, Office 365 (O365), Exchange Online, Teams, OneDrive for Business, M365 Copilot and SharePoint Online environments based on Deloitte's Microsoft 365 Cyber Risk Framework. This can include leveraging Microsoft's security solutions such as Entra, Purview, Defender, Intune, and Sentinel.
- Oversee day-to-day activities of both onsite and offshore engineers and architects.
- Function as the primary client day-to-day interface building rapport and trust with the client.
- Perform technical health checks for these M365 platforms/environments prior to broader deployments.
- Assist clients with transitions to the Microsoft 365 security services such as solution setup and service configuration, focused on risk mitigation.
- Provide technical support for M365 E5 security services and resolve service-related issues through research and troubleshooting and working with Microsoft.
- Implement industry leading practices around M365 E5 cyber risks and cloud security for clients.
- Design and develop cloud-specific security policies, standards and procedures e.g., O365 tenant management and configuration, identify management and access control, auditing and monitoring, security incident and event management, data protection (classification/labeling, DLP, encryption), user and administrator account management, SSO, conditional access controls and password/key management.
- Troubleshoot system level problems in a multi-vendor, multi-protocol network environment.
- Document platform technical issues, analysis, client communication, and resolution as part of cyber risk mitigation steps.
- Execute on M365 security engagements during different phases of the lifecycle - Discover, Assess, Design, Deploy/Test, Hypercare/Handover.
- Provide internal technical training to Advisory personnel as needed.
- Act as a subject matter expert on cloud cyber risk for Microsoft Purview, Microsoft Intune, Microsoft Defender, and Microsoft Sentinel capabilities.
- Manage to Point-of-Views (PoVs) on providing leading practices to our clients on the M365 security challenges they face.
- Contribute to eminence activities, such as whitepapers pertaining to Microsoft 365 security capabilities.
- Support talent process in the manager role such as for recruiting and coaching.
Requirements
- Working experience in at least two of the areas listed below.
- 6+ years of experience in technical consulting, client problem solving, architecting and designing solutions in a consulting role with project leadership and/or architect experience.
- 6+ years of hands-on technical experience with Microsoft 365 enterprise-level messaging and collaboration services (Teams, OneDrive for Business, Exchange Online, Entra ID, SharePoint Online, O365 administration and setup) in implementation and operations.
- 6+ years of hands-on technical experience with enterprise-level systems management systems such as SCCM and Intune and endpoint engineering (MEM) and mobile device management (MAM & MDM)) implementation or operations.
- 6+ years of hands-on technical and project / professional experience enterprise-with at least two of the following technologies: Microsoft Endpoint Security Platforms (e.g. Defender for Endpoints and Defender for Servers), Microsoft Sentinel, Microsoft's email security platform (Defender for Office), Microsoft Purview & Entra ID
Additional Requirements
- Must be willing to travel up to 50% within North America.
- Limited Sponsorship may be available.
- under Requirements.
- BA/BS Degree preferred. Ideally in Computer Science, Cyber Security, Information Security, Engineering, Information Technology.
- Microsoft Certifications such as: (SC-900, SC-100, SC-200, SC-300, SC-400)
- Cyber Certifications such as: CCSP, CCSK, CISSP, CCNP, and CCNA.