Mastering Microsoft Designer A Step-by-Step Guide, Benefits, and Use Cases
If you’ve been looking for an easy way to create stunning visuals without needing advanced design skills, Microsoft Designer might just become your go-to tool. Powered by AI, this design platform helps you create professional graphics, social media posts, invitations, and more with minimal effort. Whether you’re a business owner, marketer, or creative enthusiast, Microsoft Designer makes designing accessible for everyone. In this blog, we’ll walk you through how to use Microsoft Designer, explore its key benefits, and highlight real-world use cases where it shines. https://dellenny.com/mastering-microsoft-designer-a-step-by-step-guide-benefits-and-use-cases/
What's difference creating Agent from Copilot page vs from Copilot Studio -> Copilot for M365?
Hello, I am learning about Copilot and was very confused by these two different ways to do it. My understanding is both are "Declarative Agents" which lets the Microsoft 365 Copilot do the most heavy lifting. Method 1. First way is to go to Copilot page and clicking 'Create an Agent' w3 Method 2: Going to Copilot Studio -> Agents -> Copilot for Microsoft 365 -> New Agent (Couldn't find a screenshot) Q1. Anyway, first, I created an Agent using the first Method 1 above, and now I see it on the Copilot page under 'Agents' section. However, when I go to Copilot Studio -> Agents -> Copilot for Microsoft 365, I don't see that Agent there. Is this normal and intended? Q2. Is an Agent created using the Method 1 only available to people who have Copilot license? (as long as they are shared; I see options are only me, anyone in the organization, and specific users in the organization) Q3. Could you please confirm agents created using either way above are both "Declarative Agents"? Sorry for the newbie questions in advance... I took the course MS-4010 and reviewed several posts but still confusing...Case Study Reducing Support Ticket Volume Using AI Bots Built in Copilot Studio
In today’s fast-paced digital landscape, customer support teams are under increasing pressure to deliver quick, accurate, and personalized solutions. However, high support ticket volumes often slow down response times, frustrate customers, and increase operational costs. This case study explores how one organization successfully reduced its support ticket volume by leveraging AI bots built in Copilot Studio. https://dellenny.com/case-study-reducing-support-ticket-volume-using-ai-bots-built-in-copilot-studio/Multi-Turn Conversations and Context Management in Copilot Studio
A multi-turn conversation is one where the agent doesn’t just respond to a single question, but carries over context across several exchanges: prior user messages, system prompts, data uploaded by the user, variables set earlier, etc. The agent uses that context to produce more relevant, coherent, and efficient dialogues rather than resetting at every question. https://dellenny.com/multi-turn-conversations-and-context-management-in-copilot-studio/How MCP Works in Microsoft’s AI Ecosystem
MCP is an open standard (originated by Anthropic) whose goal is to standardize how AI models, agents, and applications interact with external tools, memory/data sources, and APIs. Instead of every AI model having its own custom glue code for every tool or database, MCP defines a consistent, structured interface for those integrations. https://dellenny.com/how-mcp-works-in-microsofts-ai-ecosystem/Boost Your Startup with Microsoft AI & Copilot A Game-Changer for Entrepreneurs
Starting a business is exciting, but it’s also challenging. From managing operations to marketing and customer support, entrepreneurs wear multiple hats. Enter Microsoft AI and Copilot—tools designed to supercharge productivity, streamline workflows, and unlock innovation. Here’s how they can help your startup thrive. https://dellenny.com/boost-your-startup-with-microsoft-ai-copilot-a-game-changer-for-entrepreneurs/
Episode 0: Learning Order Matters — Vision → Storage → Apps
I first encountered Microsoft 28 years ago, when I changed jobs. Since then my routine was simple: Outlook for mail Excel for data PowerPoint for reports Save everything to the Z or D drive That felt “enough.” Other apps? Honestly, unnecessary. Two months ago, I heard our company would move from the Z drive to the “Z Cloud.” To understand what that really meant, I began studying Microsoft 365. At first, I tried to learn app by app. But the more I studied, the more confused I became — the big picture never appeared. That’s when I realized: the learning order is completely backwards. The right order is clear: Vision → Storage → Apps. Vision: Why these tools exist — Microsoft’s mission and future direction Storage: Where the data truly lives — OneDrive, SharePoint Apps: How each app connects to that storage Two months with this mindset gave me more clarity than decades of app-first habits. Corporate training fails for the same reason: it starts with apps. 👉 That’s why Microsoft must redesign education around Vision → Storage → Apps. But education alone is not enough. Only with the right UX/UI in Copilot Pages can that education truly support users in practice. Next: A wish for Microsoft. Stay tuned! 第0弾：学びの順番がすべて — 理念 → 保存 → アプリ 私がMicrosoftに出会ったのは28年前、転職した今の会社でのこと。 それから今日までの定番はこうでした： メールはOutlook 資料はExcel 報告はPowerPoint 保存はZドライブ／Dドライブ それで“十分”だと思っていた。他のアプリは正直、不要。 しかし、約2か月前に「会社のZドライブがZクラウドになる」と聞きました。 その意味を理解するために、私はMicrosoft 365について調べることにしました。 まずはアプリについて勉強しようとしました。 しかし、アプリ単位で学んでも混乱が深まるばかりで、全体像は見えてこない。 そこで気づいたのです —— 教育の順番が完全に逆だ ということに。 本来あるべき順番はシンプルで力強い：理念 → 保存 → アプリ。 理念：なぜこのツールが存在するのか（Microsoftの使命・未来像） 保存：データはどこに置かれるのか（OneDrive／SharePoint） アプリ：保存先とどう結びつくのか この順番に切り替えてからは、たった2か月でMicrosoft 365を深く理解できました。 多くの社内教育が失敗する理由も同じ——アプリから入ってしまうからです。 👉 だからこそMicrosoftは 理念 → 保存 → アプリ の順で教育設計を根本から見直すべきです。 しかし教育だけでは十分ではありません。 Copilot Pagesの適正なUX/UIがあって初めて、その教育が本当のサポートになるのです。 次回は、Microsoftへの願い。ご期待！Microsoft Copilot and the AI-First Enterprise A Strategic Perspective
Artificial Intelligence (AI) is no longer a futuristic concept reserved for innovation labs—it is now a strategic imperative shaping the very foundation of modern enterprises. At the center of this transformation is Microsoft Copilot, a generative AI assistant embedded across the Microsoft ecosystem. From Microsoft 365 to GitHub, Dynamics, and Azure, Copilot represents more than just a productivity tool—it is a catalyst for creating the AI-first enterprise. https://dellenny.com/microsoft-copilot-and-the-ai-first-enterprise-a-strategic-perspective/Microsoft Copilot and the AI-First Enterprise A Strategic Perspective
Artificial Intelligence (AI) is no longer a futuristic concept reserved for innovation labs—it is now a strategic imperative shaping the very foundation of modern enterprises. At the center of this transformation is Microsoft Copilot, a generative AI assistant embedded across the Microsoft ecosystem. From Microsoft 365 to GitHub, Dynamics, and Azure, Copilot represents more than just a productivity tool—it is a catalyst for creating the AI-first enterprise. https://dellenny.com/microsoft-copilot-and-the-ai-first-enterprise-a-strategic-perspective/Low-Code vs Pro-Code How Copilot Studio Bridges the Gap
In the rapidly evolving landscape of software development, two approaches have emerged as dominant forces: low-code development and pro-code development. Each offers unique advantages and challenges, catering to different audiences and use cases. With the rise of AI-powered tools, the distinction between these approaches is starting to blur — and that’s where Copilot Studio steps in. https://dellenny.com/low-code-vs-pro-code-how-copilot-studio-bridges-the-gap/
