Unified Project Context Between GitHub Copilot and Microsoft 365 Copilot

[ysdzbn2prw-eng]

🏷️ Discussion Type

Product Feedback

💬 Feature/Topic Area

Copilot Workspace

Body

Unified Project Context Between GitHub Copilot and Microsoft 365 Copilot
I would like GitHub Copilot and Microsoft 365 Copilot to support a shared, permission-aware project context that allows work to move seamlessly between planning, collaboration, and implementation.

Today, project context is often spread across:

• Requirements documents
• Meeting notes
• Emails
• Task boards
• Pull requests
• Issues
• Source code
• Developers frequently need to reconstruct project context that already exists elsewhere.

Proposed Capabilities

1. Shared project memory between GitHub Copilot and Microsoft 365 Copilot
2. Bidirectional context handoff ("Open in Microsoft 365 Copilot" / "Open in GitHub Copilot")
3. AI-generated project summaries based on issues, PRs, tasks, documents, and meetings
4. Traceability between requirements, implementation, and deliverables
5. Context-aware onboarding for new contributors
6. Support for distributed and asynchronous teams
7. Permission-aware access controls and governance
8. Example Workflow
9. Requirements and planning are created in Microsoft 365 Copilot.
10. Context is transferred into GitHub Copilot.
11. Developers implement features using GitHub Copilot.
12. Progress, blockers, and technical decisions synchronize back to a shared workspace.
13. Stakeholders receive up-to-date project summaries without requiring developers to manually recreate status information.

Benefits

1. Less context switching
2. Faster onboarding
3. Better remote-team collaboration
4. Reduced project knowledge loss
5. Improved alignment between planning and development
6. Better use of AI across the entire software lifecycle

Why This Matters

Developers spend significant time recreating context that already exists elsewhere in the organization. A shared context layer between GitHub Copilot and Microsoft 365 Copilot would allow teams to move from planning to implementation without losing information while maintaining security, traceability, and human oversight.

Thank you for considering this idea.

This proposal was also submitted through Microsoft's Microsoft 365 Copilot feedback channel because the concept spans both ecosystems. I believe a shared project context layer could significantly improve planning-to-development continuity across the broader Copilot platform.

1.docx

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐