setReaction and softDelete for channel messages broken?
Hi, I have some issues using the setReaction and softDelete APIs for channel messages in MS Teams. It’s relatively easy to reproduce for me from the the MS Graph explorer. I have a message in a channel, that I programmatically want to set a reaction for (or delete it). The user calling the setReaction API is actually also the owner of the message. This can be seeing by the first screenshot, where updating the message succeeds without problems. But if I either try to set a reaction on the message, or delete it, I’m getting a weird ACL related error message (see second and third screenshot). The fourth screenshot is the relevant part of the decoded access token used by graph explorer, showing that I do have both the ChannelMessage.Send and ChannelMessage.ReadWrite permissions set for the token that are required for the setReaction and softDelete API calls according to the docs. I’ve also tried the same on a chat channel. There setReaction does work as it is supposed to, but softDelete also fails with an error message. Any help here would be appreciated.
Using PowerApps "Send a Microsoft Graph HTTP request"
Hello I am trying to send a activity to Teams activity feed. The idea is to have a SharePoint list and if a new event or update event accurse on the SharePoint list to send a notification to Teams Activity. I started with he following code but it was not working when I updated the TeamID: Method: POST URI: https://graph.microsoft.com/v1.0/teams/{teamId}/sendActivityNotification HEADER: Content-Type: application/json BODY: { "topic": { "source": "entityUrl", "value": "https://graph.microsoft.com/v1.0/teams/{teamId}" }, "activityType": "systemDefault", "previewText": { "content": "Take a break" }, "recipient": { "@odata.type": "microsoft.graph.aadUserNotificationRecipient", "userId": "569363e2-4e49-4661-87f2-16f245c5d66a" }, "templateParameters": [ { "name": "systemDefaultText", "value": "You need to take a short break" } ] } The idea is to trigger the flow by SharePoint event Update & new. Then using the HTTP Request to Graph API and send an information with the URL of the new ITEM or FILE. In the moment some user have issues to be informed by he activity feed and it works by others. But the users who have issues get by other user informed. Its really a weird situation. The users are creating in the SitePages library ASPX files and want to inform others about the updated and new pages. Thanks in advance for the help. Kind regards MichaelAI Development Just Leveled Up
At #MSBuild 2025, Microsoft unveiled 10 game-changing innovations in Azure AI Foundry—designed to help developers like you build, scale, and deploy AI-powered apps and agents faster than ever. From multi-agent orchestration, agentic retrieval, and fine-tuning open models to edge runtimes and responsible AI built-in, Foundry is now the full-stack AI platform you’ve been waiting for. 🔧 Code with VS Code 🤝 Collaborate with GitHub ☁️ Deploy with Azure It’s all unified. It’s all AI-native. It’s all here. Start building the future: Learn more
Small icon for Power App uploaded to Teams
Hi everyone I've just uploaded a Power App to Teams for the first time and I have a slight issue with the way the icon looks once it's in Teams. In my app settings the icon size looks normal: However, when I add it to Teams, the icon looks really small: Is there anything that can be done about this? It's not the end of the world but it would look nicer if the icon on my custom app was the same size as the other app icons in Teams.Mastering Query Fields in Azure AI Document Intelligence with C#
Introduction Azure AI Document Intelligence simplifies document data extraction, with features like query fields enabling targeted data retrieval. However, using these features with the C# SDK can be tricky. This guide highlights a real-world issue, provides a corrected implementation, and shares best practices for efficient usage. Use case scenario During the cause of Azure AI Document Intelligence software engineering code tasks or review, many developers encountered an error while trying to extract fields like "FullName," "CompanyName," and "JobTitle" using `AnalyzeDocumentAsync`: The error might be similar to Inner Error: The parameter urlSource or base64Source is required. This is a challenge referred to as parameter errors and SDK changes. Most problematic code are looks like below in C#: BinaryData data = BinaryData.FromBytes(Content); var queryFields = new List<string> { "FullName", "CompanyName", "JobTitle" }; var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, data, "1-2", queryFields: queryFields, features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); One of the reasons this failed was that the developer was using `Azure.AI.DocumentIntelligence v1.0.0`, where `base64Source` and `urlSource` must be handled internally. Because the older examples using `AnalyzeDocumentContent` no longer apply and leading to errors. Practical Solution Using AnalyzeDocumentOptions. Alternative Method using manual JSON Payload. Using AnalyzeDocumentOptions The correct method involves using AnalyzeDocumentOptions, which streamlines the request construction using the below steps: Prepare the document content: BinaryData data = BinaryData.FromBytes(Content); Create AnalyzeDocumentOptions: var analyzeOptions = new AnalyzeDocumentOptions(modelId, data) { Pages = "1-2", Features = { DocumentAnalysisFeature.QueryFields }, QueryFields = { "FullName", "CompanyName", "JobTitle" } }; - `modelId`: Your trained model’s ID. - `Pages`: Specify pages to analyze (e.g., "1-2"). - `Features`: Enable `QueryFields`. - `QueryFields`: Define which fields to extract. Run the analysis: Operation<AnalyzeResult> operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, analyzeOptions ); AnalyzeResult result = operation.Value; The reason this works: The SDK manages `base64Source` automatically. This approach matches the latest SDK standards. It results in cleaner, more maintainable code. Alternative method using manual JSON payload For advanced use cases where more control over the request is needed, you can manually create the JSON payload. For an example: var queriesPayload = new { queryFields = new[] { new { key = "FullName" }, new { key = "CompanyName" }, new { key = "JobTitle" } } }; string jsonPayload = JsonSerializer.Serialize(queriesPayload); BinaryData requestData = BinaryData.FromString(jsonPayload); var operation = await client.AnalyzeDocumentAsync( WaitUntil.Completed, modelId, requestData, "1-2", features: new List<DocumentAnalysisFeature> { DocumentAnalysisFeature.QueryFields } ); When to use the above: Custom request formats Non-standard data source integration Key points to remember Breaking changes exist between preview versions and v1.0.0 by checking the SDK version. Prefer `AnalyzeDocumentOptions` for simpler, error-free integration by using built-In classes. Ensure your content is wrapped in `BinaryData` or use a direct URL for correct document input: Conclusion In this article, we have seen how you can use AnalyzeDocumentOptions to significantly improves how you integrate query fields with Azure AI Document Intelligence in C#. It ensures your solution is up-to-date, readable, and more reliable. Staying aware of SDK updates and evolving best practices will help you unlock deeper insights from your documents effortlessly. Reference Official AnalyzeDocumentAsync Documentation. Official Azure SDK documentation. Azure Document Intelligence C# SDK support add-on query field.M365 Developers Update | May 2025
Spotlight Learn how you can build advanced agents for Microsoft 365 Copilot by leveraging the Microsoft 365 Agents SDK. Join the session Get an in-depth look at building agents in Copilot Studio, with a special focus on the latest innovations and what's ahead. Add to schedule Discover how you can add more knowledge to Microsoft 365 Copilot with Copilot connectors and actions. See more details From Copilot Studio to Visual Studio and Azure AI Foundry, join this session to discover the various ways you can build agents for Microsoft 365. Register now Learn Explore how to build Microsoft Teams collaborative agents as virtual colleagues with Visual Studio Code. Sign up Join us for a session on building advanced copilot Studio agents by integrating Azure AI Search, the Azure model catalog, and Model-Context Protocol (MCP) into your agents. Learn more Build task -specific declarative agents for Microsoft 365 Copilot using advanced recipes in Copilot Studio. View session See how you can build agent in Copilot Studio with deep integration into Azure AI Foundry services. Explore more Tune into this breakout session to learn how to build declarative agents for Microsoft 365 Copilot. Save to favorites Keep up to date Microsoft build labs- Learn how to use all of the latest dev tools in our hands-on labs. Sign up Updated Teams AI library- Create even more powerful agents for Microsoft Teams. Read how LinkedIn- Get the lates news, product announcements, demos and more Follow us Community calls- Learn from our experts on a variety of Microsoft 365 platform topics. Join a call
