Event in Spanish: Jueves de Quack con @acolombiadev

Key Concepts

• Copilot Skills: A major update allowing users to define and reuse workflows within Copilot, enhancing personalization and efficiency.
• Copilot Memory (Early Access): A new feature enabling Copilot to retain context, but currently facing documentation and access issues.
• Cloud Model Updates: Availability of Cloud Open 4.5 and GPT 5.2 models within Copilot.
• Data Residency & Compliance: Enterprise Cloud now supports specifying data residency for regulatory compliance.
• Collaborative Application Development: A renewed focus on building an application together, initially envisioned for sports prediction (now World Cup related).
• Importance of Clear Documentation: A recurring theme highlighting the frustration caused by ambiguous instructions and inconsistent feature availability.

---

Jueves de CUAC - 2026 Updates & Troubleshooting

The January 8th, 2026 “Jueves de CUAC” session began with greetings and a shift in focus towards collaborative application development, specifically a project centered around the upcoming World Cup. The host revisited the original concept of building an application together, initially intended for Copa Libertadores/América predictions. A significant portion of the session was dedicated to reviewing updates from the December 2025/January 2026 changelog.

Changelog Highlights (December 2025/January 2026)

Several key updates were announced: the introduction of Skills (launched December 18th) – building on previous “modes” in Cloud Code – allowing users to teach Copilot reusable processes defined by metadata, instructions, and permitted MCP (Microsoft Cloud Partner) tools. The host emphasized the importance of focusing on skills relevant to individual team needs and encouraged community contribution to a public skills repository. Cloud Open 4.5 and GPT 5.2 models are now available within Copilot, offering enhanced capabilities. Reduced pricing for hosted services took effect on January 1st. Data Residency is now supported in Enterprise Cloud, crucial for compliance in regions with strict data regulations. Finally, Copilot and Issues Auto-Assignment now automatically assigns the user to tasks assigned to Copilot, improving task tracking.

Copilot Memory Investigation & Documentation Issues

A significant portion of the session was dedicated to troubleshooting the newly announced Copilot Memory feature (currently in preview). The host encountered difficulty locating the feature within settings, despite its mention in the changelog, which he described as “muy abstracto” (very abstract). He suspected a restriction to “preview features” but argued this should be explicitly stated. Internal investigation revealed numerous similar inquiries in Slack, indicating a widespread issue.

The host attempted to verify access through internal channels, noting his staff status should grant full access. Testing both Enterprise and personal accounts revealed differing menu options, with the feature absent in his personal account. He received confirmation from Cassedy that the feature is in “early access.” The host emphasized the importance of clear documentation for new features, stating, “Esta es la manera como uno aprende cuando hay cosas que no están bien hechas” (This is how one learns when things are not well done), framing the situation as a learning opportunity stemming from poor implementation. He promised to investigate further and provide updates via Twitter or another platform.

Recent Updates Recap

Prior to concluding, the host provided a quick recap of three recent Copilot updates: ISO de skills (Skills ISO), enabling Copilot to automatically leverage existing skills defined within a user’s Cloud environment; the availability of new models within Copilot; and Memory Usage and Data Residency, with data residency options now available for users in regions like the IU (likely the European Union) or areas in Asia, addressing data privacy concerns.

Methodologies & Real-World Examples

Throughout the session, the host highlighted the importance of skill-based workflow optimization, encouraging the identification of repetitive tasks and the creation of Skills to automate them. He shared examples including a developer integrating Cloud Code agents with WhatsApp for a mobile-based workflow, his personal workflow for creating a bilingual newsletter using Copilot for translation and GitHub Actions for deployment, and the use of Astro as a static site generator optimized for LLM parsing. He reiterated the original “Jueves de CUAC” concept of collaborative application development and encouraged experimentation and community contribution. He also emphasized personalization, stating, “Equipo, usa la herramienta que te haga feliz” (Team, use the tool that makes you happy).

---

Conclusion

The session underscored the ongoing evolution of Microsoft Cloud Copilot, with significant updates like Skills and the introduction of Copilot Memory. While these features offer substantial potential for workflow optimization and personalization, the experience highlighted the critical importance of clear documentation and consistent feature availability. The host’s troubleshooting of Copilot Memory served as a practical example of the challenges users face when navigating new features and the value of community collaboration in identifying and resolving issues. The renewed focus on collaborative application development promises to bring the “Jueves de CUAC” sessions back to their original intent of building something tangible together.