Adaptive Cards Input.Date shows mm/dd/yyyy on sample site but renders as “September 20, 2017”
Hi all, I’m using Adaptive Cards Input.Date in Microsoft Teams / Copilot Studio (Teams channel). I noticed the same card renders the date differently depending on host: On the Adaptive Cards Inputs sample page, the Due Date field shows mm/dd/yyyy (e.g., 09/20/2017). But when I copy the same JSON into Adaptive Card Designer (and similarly inside Teams), the date shows as a long format (e.g., September 20, 2017). Reference page (shows mm/dd/yyyy): https://adaptivecards-release-ci.azurewebsites.net/samples/Inputs.html I want the date displayed as mm/dd/yyyy in Teams (and ideally allow typing in that format), e.g. 12/20/2025. { "type": "AdaptiveCard", "$schema": "http://adaptivecards.io/schemas/adaptive-card.json", "version": "1.5", "body": [ { "type": "TextBlock", "text": "Due Date" }, { "type": "Input.Date", "id": "DateVal", "value": "2017-09-20" } ] } Questions Is it possible to force the display format of Input.Date to mm/dd/yyyy via Adaptive Card schema/JSON? Or is the display format always controlled by the host (Teams) / locale and cannot be overridden? If it cannot be forced, what’s the recommended workaround in Teams? Example: use Input.Text with validation? or show helper text under the field? Environment: Adaptive Cards in Teams via Copilot Studio. AshishTyped input routing stops working after navigating back to Home topic via Action.Submit (Invoke)
We are building a Copilot Studio agent with this structure: Home topic (menu page with icons) FeatureTopicA / FeatureTopicB / FeatureTopicC / FeatureTopicD Routing based on typed text (e.g. “feature A”, “feature B”) using a topic with trigger “A message is received” Navigation between topics using Action.Submit buttons (Invoke), including a Home / Back icon Observed behavior On a fresh conversation: Typing keywords like feature A or feature B correctly routes to the expected topic. From any feature topic, clicking Home (Action.Submit → Go to Home topic): Home page loads correctly. After returning to Home, typing the same keywords: Routing does not happen The conversation remains on Home The “A message is received” router topic is not triggered Restarting the conversation makes typing work again — until Home is reached via button navigation. We already tried following Dedicated router topic with trigger “A message is received” and highest priority Clearing global/custom variables when returning to Home Forcing routing using global flags Ensuring Home topic has no message trigger and no phrases Using Invoke-only navigation topics Handling text via Recognizer.TriggeringMessage.Text, LastMessage.Text, etc. Core questions Is this expected behavior in Copilot Studio? After navigating to a topic via Action.Submit (Invoke), does that topic “own” subsequent typed messages? What is the recommended pattern if users must be able to: Navigate via Home / Back buttons Then type free-text on the Home page Have typed text routed reliably every time Is the intended design: Home topic acts as the router itself? Or only one global message-received router should exist? Or typed input should not be expected to work reliably after Invoke navigation? We want to allow users to: Use menu buttons for navigation Return to Home Still type free-text commands Have routing work consistently without restarting the conversation Any official guidance, known limitations, or best-practice patterns would be greatly appreciated.
How to make the most of Copilot in Human Resources?
Here is a bit of a different question than I have seen in this forum. What are some best practices and interesting use cases you all have seen with Copilot in HR departments? I want to make sure our team is using it effectively. Any automation scenarios or hr tools that integrate with Copilot?Copilot Chat vsus. Microsoft 365 Copilot What's the difference?
While their names sound similar at first glance - Microsoft 365 Copilot and Microsoft 365 Copilot Chat - they differ in several aspects. And more importantly, one can't be without another. What is Microsoft 365 Copilot Chat? First since first. Microsoft 365 Copilot Chat is also called Copilot Chat. Copilot Chat generates answers based on web content, while Microsoft 365 Copilot is also grounded on users' data, like emails, meetings, files, and more. Since January 15, Microsoft 365 Copilot Chat is available for everyone. Everyone in organizations. Also customers with a Microsoft 365 Business Basic subscriptions can enjoy using Copilot Chat securily. The screenshot below shows how Copilot Chat looks like and highlights its main capabilities. Note that EDP - Enterprise Data Protection is available. What is Microsoft 365 Copilot? Microsoft 365 Copilot is an add-on available for specific Microsoft 365 Subscriptions: Microsoft 365 E3, E5, A3, A5, and Business Standard & Premium. It includes Copilot Chat in addition to other Copilot features: Microsoft 365 Copilot also includes a chat grounded on users' meetings, emails, chats, and documents. It integrates into Microsoft 365 apps, like Outlook, Teams, Word, Excel, and more. It brings the capability to create agents and additional Copilot management features such as SharePoint Advanced Management and Copilot Dashboard. The screenshot below shows how the Copilot chat experience for those users who got the Microsoft 365 Copilot license. Note that EDP - Enterprise Data Protection is available here too. Copilot Chat can be pinned in MS Teams and MS Outlook as App. How can I access Microsoft 365 Copilot Chat? Copilot Chat is nowadays accessible via m365copilot.com using your Entra account. In contrast to Microsoft 365 Copilot licensed users, Microsoft 365 Copilot Chat users cannot see, by default, Copilot Chat pinned on the Microsoft 365 homepage. Microsoft 365 Copilot Administrators will have to pin the chat in the admin center so it is easy for Copilot Chat users to access it. What's the difference? There are some aspects, such as licensing requirements, subscription fees, data sources, or access to organization content, that determine the differences between Copilot Chat and Microsoft 365 Copilot. I have listed it in the screenshot below. 👇 Image showing a 3-column table: Aspect, Microsoft 365 Copilot Chat, and Microsoft 365 Copilot.Overview of Copilot solutions and Key Benefits
Copilot isn’t one-size-fits-all. Each solution addresses different organizational needs. Here’s what they do—and why they matter. Microsoft 365 Copilot Chat is a conversational experience on web and mobile that delivers quick, context-aware answers from organizational data. It provides quick, context-aware answers from organizational data, improving responsiveness across departments while supporting mobile work scenarios. Microsoft 365 Copilot is an AI assistant built into Word, Excel, PowerPoint, Outlook, and Teams. It accelerates document creation, data analysis, and presentations and helps you catch up on meetings and messages. Copilot uses the context you already have in Microsoft 365—files, emails, chats, and calendars—through Microsoft Graph and respects the same permissions, security, and compliance your organization relies on. Microsoft Copilot Studio is a platform for extensibility and customization. It lets you build custom copilots and extend existing ones without writing code. Copilot Studio allows businesses to tailor AI to unique workflows without heavy development investment, accelerating innovation. Key benefits for organizations Copilot delivers three core benefits that impact the entire organization: Benefit How benefit achieved Example scenario Boost productivity by automating repetitive tasks. Copilot automates repetitive tasks and accelerates content creation across teams. A marketing team might use Copilot in Word to draft campaign briefs based on brand guidelines, reducing turnaround time from days to hours. Improve decision quality with data-driven insights. Copilot provides fast, data-driven insights, enabling better decisions at every level. An operations team might use Copilot in Excel to analyze supply chain data and identify cost-saving opportunities before quarterly reviews. Strengthen governance with enterprise-grade compliance. Copilot respects enterprise security and compliance standards, ensuring sensitive data stays protected. When legal teams draft contracts, Copilot uses only authorized organizational data through Microsoft Graph, maintaining compliance with internal policies and regulatory requirements.
Change Default for Copilot Automatic Room Rebooking Setting in Outlook?
My users with Microsoft 365 Copilot licenses have noticed a newer feature that automatically rebooks meetings with an alternate room if the selected room is unavailable. It appears that this setting is on by default and can be turned off on a per case basis when a new meeting event is being scheduled. Is there a way to turn it off by default and allow people to enable it when a new calendar item is being created instead? Here is what it looks like for me in Outlook. I can click on Edit from the new meeting window and turn it off for a single event. I haven't found a way to change that default behavior. Has anyone found a way to adjust this? Thank you! BrianSo many different CoPilots - confusing, unproductive
I think we have all learned that CoPilot is a brand, a suite of tools. That probably makes sense from Microsoft perspective, but it is confusing as heck for end users or people trying to roll out CoPilot in a company. Products include: Sharepoint agents CoPilot desktop app Copilot in Office apps -- different copilots for PPT, Word, excel, Outlook CoPilot Studio - custom copilots (which by the way turn into "apps"???) Teams Copilot Researcher and Analyst Agents Prompting Coach Visual Creator What is even more frustrating is they don't all work together or in the same environments. I want to call my Sharepoint Agent from my Copilot, nope. I want my Custom Copilot to use Researcher (or vice versa even), not happening (despite Copilot giving me instructions on how it should). Meanwhile, in Anthropic-land, I setup an MCP service to integrate Claude and my to do app. Not without hiccups, but it works now. The whole Copilot ecosystem needs to get a lot more consistent and quickly or you are going to continue to loose users. PS - as i went to post this, I needed to select Tags -- there were 20 Copilot products to choose from!
usage reporting for shared agents (created in teams with agent builder) not possible
Dear all, in my organisations I have a vivid community of Copilot users that create agents in teams (with agent builder) and share them amongst other users. Those agents are also visible then in the admin center in the Copilot section as category "Shared" which works as expected. When I now try to understand what agents are used the most I go to the Copilot usage report (Reports -> M365 Copilot -> Copilot -> Agent details), I see a list of agents with active user information. However only App ID (no names and no external App ID) without a name. my questions: I am wondering what agents are shown here. Because I have about 100 shared agents and this reports has only a small number of agents listed I tried all the suggested things (in the guides)to get a name for the App ID (through teams managed Apps list, entra app list etc.) but was not successful to get a clear name for those App ID Is there any way to geht a usage report for shared agents (we do not use Copilot studio at the moment) Many thanks for your thoughts and helps..I feel we are at a dead end at the moment and the recent anouncments did not yet convince me that then we can report shared agent usage... kind regardsThe Instruction Story — Prologue
Microsoft 365 apps are incredibly powerful. Yet within their intertwined features and ever-evolving UX/UI, users often get lost — overwhelmed by complexity and constant change. As a result, many people stop trying to truly understand, relying instead on Excel alone. This isn’t just a workplace issue; it’s a challenge in classrooms as well, where learning often halts before understanding can take root. In my previous Tech Community post (Part 0), I wrote about the moment of “realization” — the instant when understanding clicks into place. That experience led me to a new experiment: A user’s manual told as a story — “The Instruction Story.” This story follows a traveler and a small fairy named Copilot, as they wander through the world of Microsoft 365 — sometimes lost, sometimes pausing — to learn how its structures and systems truly connect. At the end of this journey, you too may find yourself realizing something. What that is, we do not yet know. And so, The Instruction Story begins. I hope to grow this journey together with the people of Microsoft, as companions in understanding. ※ This story is written by momotarou, from a user’s perspective. Some parts may feel unusual from a technical standpoint, but it is written with the utmost respect for “understanding” as the heart of learning. 取説物語 ― まえがき ― Microsoft 365 の各アプリは非常に優れています。 しかし、その関係性や複雑に重なり合う機能、 そして進化し続ける UX/UI の中で、ユーザーは迷い、時に混乱し、気づけば迷子になりがちです。 その結果、多くの人々は理解することをあきらめ、Excel に依存し続けてしまう現状…。 各アプリの学びの中断は、職場だけではなく教育現場でも同じです。 以前、私は Tech Community の 0 弾で「理解するための気づき」について書きました。 それをきっかけに、私は新たな試みを始めようと考えました。 それが―― **物語としての取扱説明書『取説物語』**です。 この「取説物語」は、Microsoft 365 の世界を旅する“旅人”と、 小さな妖精“コパイロット”が、時に迷い、立ち止まりながら、 Microsoft の世界の仕組みや構造を学ぶ物語です。 旅の終わりには、あなたも何かに気づくかもしれません。 それが何なのかは、現時点ではわかりません。 では、取説物語の開幕です。 Microsoft の皆様と共に、この物語を育てていければと願っています。 ※ この物語は、@momotarou が見た Microsoft の世界を、学び人の視点から描いた教育物語です。 技術者や開発者の方から見ると、表現や構成に違和感を感じることもあるかもしれませんが、 筆者はユーザーの「理解」を最も重視して執筆しています。あらかじめご了承ください。
