IAM Meeting - razmipatel/Random GitHub Wiki

Meeting Notes Template – Identity Services Transition to BAU
Purpose: Capture all required information and documentation for handover of Azure/Entra ID–based Identity Services into BAU.

1. Meeting Details

  • Date & Time:

  • Attendees:

    • Identity Team:

    • Cloud Security/Transition Team:

  • Facilitator:

  • Note-taker:

2. Objectives

  1. Identify and collect all service documentation required by the transition checklist.

  2. Clarify process ownership, handover timelines, and storage locations.

  3. Surface any gaps or risks to address pre-BAU.

3. Agenda & Discussion Points

Domain | Control Item | Key Questions | Info Captured / Actions | Owner | Due -- | -- | -- | -- | -- | -- A. Documentation | Service description | – What is the formal service description? – Where is it maintained? |   |   |     | Service contract | – Which ADM teams are in scope? – Where is the signed contract or MoU? |   |   |     | High-Level Design (HLD) | – Do we have HLD diagrams (network, identity flows, components)? – Format and version? |   |   |     | Cyber/security analysis | – Where are the threat models or risk assessments? – Date of last update and owner? |   |   |     | Infrastructure inventory | – Complete list of Azure tenants, subscriptions, Entra ID components. – CI identifiers in CMDB? |   |   |     | Network flow matrix | – Documented ingress/egress flows (e.g. Conditional Access, firewall rules)? – Where to find it? |   |   |     | Operations handbook | – Run-book for daily/weekly/incident tasks? – Location (Confluence/SharePoint)? |   |   |     | Policies | – Security, backup, retention, patching, tagging, naming conventions. – Are they published centrally? |   |   |     | SOPs | – Backup, restore, patching, certificate management, user-lifecycle management. – Where to access latest versions? |   |   |     | Scheduling plan | – Maintenance windows, change windows. – Who approves and where is the schedule stored? |   |   |     | DRP & test results | – DR plan for Entra ID failover scenarios. – Evidence of last test (date/outcome)? |   |   |  

| B. Organization & RACI | RACI matrix | – Who is Responsible/Accountable/Consulted/Informed for each service activity? <br>– Where is the RACI stored? | | | |

| C. ITSM Processes | Incident management | – Incident lifecycle: tool, SLA, escalation paths, notification lists. | | | |
| | Problem management | – Known-error process, root-cause analysis workflow. | | | |
| | Request management | – Onboarding/offboarding, password resets, access requests. <br>– Templates, forms, portals? | | | |
| | Change management | – Standard vs. emergency changes. <br>– CAB schedule, pre-checks, rollback plans. | | | |
| | Service-level management | – SLA definitions (MTTR, MTTA, RTO/RPO). <br>– Reporting cadence and dashboards? | | | |

| D. SOPs & Operational Tasks | Antivirus & security agents | – Which endpoint security tools cover identity servers? <br>– Update/monitoring procedures. | | | |
| | Backup & VM restoration | – Backup schedules, retention, restore tests. | | | |
| | Patching | – Patch cadence, test plan, approval process. | | | |
| | Assets monitoring | – Dashboards for health, patch status, vulnerabilities, tagging, naming. <br>– Alert thresholds, run-book actions. | | | |

| E. Technology & Compliance | CIs compliance in CMDB | – Are all Configuration Items in CMDB? <br>– Data accuracy and update process? | | | |
| | Logging & monitoring | – Which logs (Sign-in, audit, provisioning) are retained? <br>– Retention period and SIEM integration? | | | |
| | Alerting & dashboards | – Key security and availability KPIs. <br>– Responsible support group for alerts. | | | |
| | Compliance & audit | – Regulatory or internal compliance standards (e.g. GDPR, ISO 27001). <br>– Evidence and audit schedule. | | | |

| F. Additional Topics | Support model | – Tier 1/2 support teams, escalation to Microsoft support. <br>– On-call rota and contact lists. | | | |
| | Knowledge transfer | – Outstanding KT sessions, recordings, decks. | | | |
| | Roadmap & enhancements | – Planned identity features (PIM-rollout, entitlement mgmt). | | | |

4. Next Steps & Action Items

  1. Assign owners to each documentation item and process.

  2. Populate links and evidence in the checklist spreadsheet.

  3. Schedule follow-up for any outstanding gaps by [date].

⚠️ **GitHub.com Fallback** ⚠️