We'll be kicking off 2025 with a session from one of our members, Ash Sadek, on Copilot! See below for the details on his session. We're also going to try combining education with socialization instead of having two separate events, so this January event will have content first and then a fully optional happy hour nearby afterwards.
Please note that we will be at the Microsoft office in Edina (Centennial Lakes) as our location (pending confirmation), which means that we have to collect more information than normal to register: full name, company, email, and phone.
# Agenda
- 3:00 - Welcome and chapter news
- 3:10 - Your 1st Copilot – Adopting Business Transformation, with Ash Sadek
- 4:30 - Impact of data events and recovery on Copilot and AI presented by Own Company, with Alan Garcia
- 5:00 - Happy hour and social time!
-----------------------------------------------------
# Your 1st Copilot - Adopting Business Transformation
Discover how to leverage the power of Microsoft Copilot and Copilot Studio to streamline your organization’s workflows and enhance productivity. In this fast-paced session, you'll get a comprehensive overview, hands-on live demos, and real-world examples to see how adopting these tools can transform your business operations.
## What You'll Learn:
· Using Copilot (and GenAI tools) for Work:
o Emphasis on Data Privacy and Commercial Data Protection
· M365 Copilot Overview:
o Core functionalities and benefits
o Extending its OOTB functionality with Copilot Studio
· Copilot Studio Overview:
o Key components and RAG capabilities
o Live Demo: Creating your 1st bot
o Real-World Use Case: Supply Chain Informational Bot
o Agentic Capabilities: What’s next in the industry?
· Q&A and Resources:
o Get answers, quick-start guides, and real-world references.
# Impact of Data Events and Recovery on Copilot and AI
Our session will focus on how Copilot and AI is dependent on data to function at all, let alone function well, but when data events occur, there is a direct downstream impact on what Copilot will return. We will emphasize the need to recover from loss and corruption events quickly to allow AI to "repair" itself faster and minimize risk impacts to poor AI outputs.
