Mid Microsoft Power Platform Governance Lead

We need to output HTML fragment with sections: About the role? The posting includes Overview, Responsibilities, Qualifications, Preferred Qualifications, Benefit And Compensation Transparency. Also maybe "Overview" could be considered "About the role". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to include sections only if real content. We have: - Overview (about the role) -> could be "About the role". It contains description of company and role. Should be included. - Responsibilities: a long list. Should be a section with heading

  Responsibilities

  and then
  • each bullet. - Qualifications: includes required qualifications (Bachelor's degree etc). Should be a section

    Qualifications

    with list. - Preferred Qualifications: could be considered "Skills" or maybe separate "Preferred Qualifications". The instruction list includes Skills as possible heading. But we can also keep "Preferred Qualifications" as a heading? The examples given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications explicitly, but we could treat it as "Skills" or maybe "Qualifications" includes both required and preferred? Better to separate: we could have "Qualifications" for required, and "Preferred Qualifications" as a separate section maybe under "Skills". However instruction says include a section ONLY when posting has real, specific content for it. It does have preferred qualifications content. So we should include a section. Which heading? Could use "Preferred Qualifications" as heading, but not in the examples. Might be okay to use "Preferred Qualifications" as heading, but they said use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests those are examples, not exclusive list. So we can use "Preferred Qualifications". However they also say "Prefer a few substantive sections over many thin ones." Might be better to combine Qualifications and Preferred Qualifications into one "Qualifications" section with subheadings? But they want

    • for any list. Could have two lists: Required Qualifications and Preferred Qualifications within same section using

      ? Not allowed? Only

      for section headings. Could embed inside

      . But better to keep separate sections: Qualifications (required) and Preferred Qualifications (maybe as "Skills"). Benefit And Compensation Transparency: includes benefit list and pay range. So we need Benefits and Pay sections. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. It does state benefits and pay range. So we should include Benefits and Pay sections. Possibly combine them? Could have Benefits section with list of benefits, and Pay section with pay range. Or combine into one "Benefits and Compensation" section. The examples include Benefits and Pay separate. We'll follow that. Schedule: not mentioned, so omit. We need to remove boilerplate: EEO, application instructions, contact info, etc. Also remove duplicated lines. We need to preserve all substantive information: overview text, responsibilities list, qualifications list, preferred qualifications list, benefits list, pay range. We must not invent or summarize away detail. Keep details as is. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Overview paragraph: "Overview At ITA International, we ’ re a tech-enabled professional services company. Headquartered in Newport News, Virginia, we leverage subject matter expertise, data analytics and technology to challenge boundaries and transform possibilities. With a global presence and a passionate team of over 200 ITAers, we ’ re driven by mission success for our customers, “ In The Arena. ” Our expertise spans Operations, Training, Engineering, Nanotechnology, Statistics, Machine Learning and Software Engineering – enabling data and tech-enabled solutions that deliver real value. Join our impactful journey at ITA International. As Theodore Roosevelt said, “ The credit belongs to the man who is actually in the arena. ” We ’ re here, standing beside our customers , ready to serve and succeed. ITA is seeking a Mid-Level Microsoft Power Platform Governance Lead to join the team in Fort Eustis, Virginia in a hybrid position." We need to keep that as prose under About the role. Responsibilities: list of bullet points after "Key Responsibilities". Actually there is a paragraph before "Key Responsibilities": "The Governance Lead will support the establishment, implementation, operation, and continuous improvement of a secure and scalable governance framework for Microsoft Power Platform capabilities. The Governance Lead will help ensure that Power Apps, Power Automate, Co-Pilot studio, Power BI, Dataverse, connectors, environments, solutions, and related platform capabilities are developed and operated consistently with organizational policies, security requirements, enterprise architecture standards, and mission needs. Working closely with Solutions Architects, Microsoft Cloud Architects, Power Platform Developers, Business Analysts, cybersecurity personnel, data owners, system administrators, and government stakeholders, the Governance Lead will establish practical controls that enable innovation while reducing security, compliance, operational, and technical risks. The ideal candidate will have hands-on experience with Power Platform administration and governance, including environments, security roles, Data Loss Prevention (DLP) policies, connectors, Application Lifecycle Management (ALM), solution management, capacity, monitoring, reporting, and the Microsoft Power Platform Center of Excellence approach." Then "Key Responsibilities" heading and then bullet list. We should include all that as responsibilities. Could treat the introductory paragraph as part of responsibilities prose, then list. We'll output

      Responsibilities

      then maybe a

      for the intro paragraph, then

      • for each bullet. Let's extract bullet points: - Support the development, implementation, and continuous improvement of the T2COM Power Platform governance framework. - Establish and maintain Power Platform governance standards, procedures, policies, and operating processes. - Support Power Platform environment strategy, including development, test, training, staging, and production environments. - Administer and monitor Power Platform environments in accordance with approved policies. - Support implementation and management of Data Loss Prevention (DLP) policies. - Evaluate connectors and integration technologies for security, compliance, and operational suitability. - Establish standards for Power Apps, Power Automate, Power BI, Dataverse, and related Power Platform capabilities. - Configure and support Power Pages within the Power Platform, including licensing, security scanning, site configuration, visibility, and user access to ensure secure and appropriately governed external-facing solutions. - Support Power Platform Application Lifecycle Management and solution management. - Establish standards for development, testing, deployment, versioning, and production support. - Monitor Power Platform usage, capacity, environments, applications, flows, and other platform resources. - Develop governance dashboards and reports to provide visibility into platform adoption, usage, compliance, and risk. - Identify unmanaged, orphaned, inactive, or non-compliant applications and workflows. - Establish processes for application and workflow inventory management. - Support Power Platform Center of Excellence (CoE) capabilities and governance processes. - Develop and maintain Power Platform standards, naming conventions, documentation requirements, and development guidelines. - Review proposed Power Platform solutions for compliance with established governance standards. - Work with developers and architects to resolve governance and platform issues. - Support security reviews of applications, workflows, connectors, environments, and data access. - Coordinate with cybersecurity personnel on security findings, vulnerabilities, access issues, and compliance requirements. - Support identity and access management using Microsoft Entra ID and Power Platform security roles. - Apply least-privilege principles to Power Platform environments and solutions. - Establish processes for environment provisioning, access requests, application onboarding, and retirement. - Support platform onboarding and offboarding processes. - Develop governance guidance for citizen developers, power users, and professional developers. - Establish guardrails that enable appropriate citizen development while protecting enterprise and mission data. - Provide governance guidance and technical consultation to development teams. - Support Power Platform adoption and enablement initiatives. - Develop training, documentation, and communications related to governance requirements. - Monitor compliance with established platform policies and procedures. - Identify technical debt, redundant applications, duplicative workflows, and unsupported solutions. - Participate in architecture reviews and technical governance boards. - Maintain governance documentation and compliance evidence. - Support audits, assessments, and authorization activities as required. - Perform other Power Platform governance and administration duties as required. Now Qualifications (required): "Bachelor's degree in Computer Science, Information Systems, Information Technology, Cybersecurity, or a related technical discipline, or equivalent professional experience. 5+ years of experience in IT, application development, systems administration, cloud administration, or related technical fields. 3+ years of experience working with Microsoft Power Platform or closely related Microsoft technologies. Demonstrated experience with Power Platform administration, configuration, or governance. Hands-on experience with: Power Apps - Power Pages on the Power Platform Power Automate Power BI Co-Pilot Studio Dataverse Power Platform environments Solutions and ALM Experience managing or supporting Power Platform environments and security. Experience with Data Loss Prevention (DLP) policies and connector governance. Understanding of Microsoft Entra ID, security roles, permissions, authentication, and authorization. Understanding of Power Platform licensing, capacity, environments, and platform administration concepts. Experience developing technical standards, procedures, and governance documentation. Experience working with application development and deployment lifecycle processes. Understanding of data security, privacy, access control, and information-handling principles. Experience working with technical and business stakeholders. Strong analytical and problem-solving skills. Strong written and verbal communication skills. Ability to work independently and coordinate activities across multiple technical teams. Ability to obtain and maintain the required security clearance." We need to format as list. Some items have sub-items (Hands-on experience with: list). We can treat each as separate
      • maybe with nested
        . But instruction: Use
        • for any list of duties/requirements/benefits. Could nest. We'll produce:

          Qualifications

          • Bachelor's degree in Computer Science, Information Systems, Information Technology, Cybersecurity, or a related technical discipline, or equivalent professional experience.
          • 5+ years of experience in IT, application development, systems administration, cloud administration, or related technical fields.
          • 3+ years of experience working with Microsoft Power Platform or closely related Microsoft technologies.
          • Demonstrated experience with Power Platform administration, configuration, or governance.
          • Hands-on experience with:
            • Power Apps - Power Pages on the Power Platform
            • Power Automate
            • Power BI
            • Co-Pilot Studio
            • Dataverse
            • Power Platform environments
            • Solutions and ALM
          • Experience managing or supporting Power Platform environments and security.
          • Experience with Data Loss Prevention (DLP) policies and connector governance.
          • Understanding of Microsoft Entra ID, security roles, permissions, authentication, and authorization.
          • Understanding of Power Platform licensing, capacity, environments,