<!-- Due to indented blocks for lists within admonition blocks --> <!-- markdownlint-disable MD046 -->

Phase 3: Verification & Next Steps

**[← Previous: Development Tools](onboarding-tools/)** | **[Back to Overview](onboarding/)**

Verify all access is working correctly, troubleshoot any issues, and plan your first weeks on the team.

**Estimated Time:** 30 minutes

---

Phase 3 Checklist

• Complete comprehensive access verification
• Resolve any troubleshooting issues
• Review essential reading materials
• Plan your first week goals

---

Access Verification

Validate your access and ensure everything is working correctly.

Complete Verification Checklist

- [ ] Can access [Epic on Azure Organization](https://github.com/optum-tech-compute)
- [ ] Can clone repositories with your SSH key
- [ ] Can create branches and pull requests
- [ ] Can view issues and project boards

- [ ] Can login to [Azure Portal](https://portal.azure.com) with cloud ID
- [ ] Can view assigned subscriptions and resource groups
- [ ] Can navigate Azure resources (VMs, networking, etc.)
- [ ] Can access Azure CLI/PowerShell (if configured)

- [ ] Can access [Terraform Enterprise](https://arc.optum.com/terraform/)
- [ ] Can view workspace lists and state files
- [ ] Can access [HashiVault namespaces](https://vault.uhg.com/ui/)
- [ ] Can browse secret engines and paths

- [ ] Can access Dynatrace dashboards
- [ ] Can run basic Splunk queries
- [ ] Can view system health metrics
- [ ] Can filter data using Epic-specific tags

Verification Testing Commands

Once you have your developer workstation set up, test these commands:

# Test GitHub access
git clone [email protected]:optum-tech-compute/ohemr-epic-megadoc.git

# Test Azure CLI (if configured)
az account list
az group list

# Test Terraform (if CLI configured)
terraform version

---

Troubleshooting Common Issues

Access Problems

!!! failure "Access Denied Errors"

1. Verify group membership in [secure.uhc.com](https://secure.uhc.com) → My Access
2. Check if access requests are still pending approval
3. Ensure you're using the correct User ID for each platform
4. Some permissions can take up to 48 hours to propagate

!!! failure "Multi-Factor Authentication Issues"

1. Ensure MS Authenticator is configured correctly
2. For Azure: Use authenticator app, not SMS when possible
3. Contact IT Help Desk if MFA reset is needed
4. Clear browser cache if getting authentication loops

!!! failure "VPN/Network Connectivity"

1. Ensure corporate VPN is connected
2. Verify DNS resolution for internal URLs
3. Check firewall settings for development tools
4. Try different browsers if having persistent issues

Platform-Specific Issues

!!! failure "GitHub Issues"

- **SSH Key Problems:** Ensure your SSH key is added to GitHub
- **Organization Access:** Verify you accepted GitHub organization invite
- **Repository Access:** Some repos require additional team membership

!!! failure "Azure Portal Issues"

- **Subscription Not Visible:** Check if using correct account (@optumcloud.com)
- **Resource Access Denied:** Verify resource group permissions
- **MFA Loops:** Clear browser cache and cookies

!!! failure "Terraform/Vault Issues"

- **Workspace Not Visible:** Confirm project-specific group approval
- **Vault Access Denied:** Ensure only Read OR Write access requested
- **Connection Timeouts:** Check VPN and network connectivity

---

Essential Reading

Complete these materials in your first week to understand team processes and standards.

Must-Read Documentation (Complete in First Week)

1. Developer Workstation Setup - Configure your development environment
2. Rules of the Road - Team policies and best practices
3. GitHub Workflow - Our development process and standards
4. Contributing Overview
5. Writing Standards
6. Publishing Process
7. Submodules Guide
8. Support & FAQ

Important Architecture Documentation

• Best Practices - Team standards, conventions, and high-level platform design
• Security Guidelines - Security requirements and best practices
• Infrastructure Patterns - Common infrastructure designs
• Monitoring Strategy - How we monitor and alert

Team Resources

• MEGADOC Home - Complete documentation portal
• Best Practices - Team standards and conventions
• Troubleshooting Guides - Common problem solutions

---

First Week Goals

Plan your first week activities to integrate smoothly with the team.

Week 1 Objectives

• Complete workstation setup and tool installation
• Join all team communication channels
• Attend onboarding meetings with team leads
• Review key architectural documentation
• Complete first small contribution (documentation fix, etc.)
• Shadow a team member during daily work
• Participate in team standups and meetings

Ongoing Learning

Architecture Reviews: Monthly deep-dives into platform design

• Join the monthly architecture review meeting
• Review previous meeting notes and decisions
• Prepare questions about system design

Lunch & Learns: Bi-weekly technical presentations

• Attend upcoming sessions
• Suggest topics you'd like to learn about
• Volunteer to present on your expertise

Certification Paths: Azure and Epic certification guidance

• Discuss certification goals with your manager
• Access company-sponsored training resources
• Plan study schedule around work responsibilities

Mentorship Program: Paired with experienced team member

• Meet with your assigned mentor
• Set expectations and communication cadence
• Plan knowledge transfer sessions

---

Getting Help

Know where to get support for different types of issues.

Support Channels by Issue Type

!!! question "Technical Questions"

- 💬 **Teams Channel:** #epic-azure-support channel
- 🐙 **GitHub Discussions:** Create discussion in relevant repo
- 📚 **Documentation:** Check [MEGADOC](../) first
- 🎓 **Lunch & Learn:** Bi-weekly technical sessions

!!! question "Access/Security Issues"

- 🎫 **IT Help Desk:** Standard corporate IT support
- 🔒 **Security Team:** For security-related access issues
- 👥 **Team Leads:** For role-specific access questions
- 📋 **Secure Portal:** [secure.uhc.com](https://secure.uhc.com) for group requests

!!! question "Business/Process Questions"

- 👨‍💼 **Team Lead:** Your direct reporting manager
- 📊 **Project Managers:** For project-specific guidance
- 🏗️ **Architecture Team:** For technical design questions
- 🎯 **Product Owner:** Feature and requirement clarification

Escalation

For incident severity, on-call rotation, and escalation paths, follow the authoritative procedures published by the platform operations team rather than any timing in this onboarding doc. Start with #epic-azure-support for non-urgent issues and your manager / on-call for urgent issues.

---

Welcome to the Team

Congratulations! You now have all the access and knowledge needed to contribute to our Epic on Azure platform. Our team is excited to work with you and see the unique perspectives and skills you bring.

**Remember:** Don't hesitate to ask questions. We'd rather answer the same question multiple times than have you struggle in silence.

Your Next Steps

1. 🔧 Set up your development environment — Install and configure development tools.
2. 📖 Study team guidelines — Learn our development standards.
3. 🤝 Schedule 1:1 meetings — Meet with your manager and key team members.
4. 📝 Complete your first contribution — Start with a small documentation improvement.
5. 🎯 Join team meetings — Participate in standups, planning, and reviews.

First Contribution Ideas

Easy First Tasks:

• Fix a typo or improve wording in documentation
• Add a missing link or update an outdated URL
• Contribute to a GitHub discussion or issue
• Update team contact information or meeting details

Slightly More Complex:

• Add examples to existing documentation
• Improve formatting or organization of a guide
• Create a simple automation or utility script
• Review and update onboarding materials based on your experience

---

Feedback & Continuous Improvement

Your fresh perspective is valuable! Please share feedback about:

- **Onboarding Experience:** What was confusing or could be improved?
- **Documentation Gaps:** What information was missing or hard to find?
- **Process Issues:** Where did you encounter friction or delays?
- **Tool Problems:** Which tools were difficult to access or use?

Ways to Provide Feedback:

• Create issues in the documentation repository
• Share feedback in team meetings or 1:1s
• Contribute improvements directly via pull requests
• Participate in onboarding retrospectives

---

Quick Reference

Essential URLs

Emergency Contacts

• Security Incidents: +1-800-SOC-HELP
• Platform Issues: Epic on Azure Teams Channel
• Access Issues: IT Help Desk

---

Phase 3 Verification & Next Steps | Epic on Azure Team Onboarding

This onboarding guide is regularly updated. If you find outdated information or have suggestions for improvement, please create an issue in our documentation repository.