Dynamics 365 & Power Platform

[Reza Dorrani @rezadorrani]

NEW Modern Screens are here in Power Apps 🚀

These new screen templates are built with 100% Modern Controls and are fully responsive by design.

Start with a polished, responsive screen and then customize it.

🎥 Watch: https://t.co/26YyBJQKJX

[Juan Carlos González @jcgm1978]

What’s new in Power Platform: July/August 2026 feature update https://t.co/oKreizQY5B #PowerPlatform #PowerApps #PowerAutomate #MVPBuzz

[Josh Cook | Microsoft MVP @FlowAltDelete]

Power CAT has quietly built one of the most important pieces of the Microsoft agent ecosystem.

A public gallery of reusable Agent Skills for Copilot Studio, Copilot Cowork and Microsoft Scout.

Nearly 80 skills already:

> Dataverse table lookup
> Power Automate documentation
> Power BI model review
> Agent evaluation
> Copilot Studio test planning

Download the instructions and optional scripts. Add them to the supported agent. Give it a repeatable way to work.

Builders can publish their own through GitHub too.

https://t.co/JswZhcTzhr

[Charles Lamanna @clamanna]

The most important thing my team will do this year won’t be a single product or feature we ship - it will be changing how we work. I wrote about the 3 things that have mattered most as we’ve changed how we build – and there’s more we’re still figuring out. https://t.co/FboBABlr7v

[Pavle Davitkovic @pavle_dav]

You’re not officially a .NET engineer until dates and times have broken your code.

Let’s make sure that happens less often.

In my experience, dates and times are much trickier to work with than they first appear.

Time zones, offsets, parsing, serialization, and daylight saving time are some of the areas I’ve struggled with the most.

And I bet you have too.

Over the years, I’ve gathered nine pragmatic tips that have made working with dates and times in .NET much easier:

1. Use UTC by default
Store timestamps in UTC whenever you need a consistent representation of an exact moment.

2. Prefer DateTimeOffset
It keeps both the moment in time and its offset, making it safer when working across regions.

3. Check DateTime.Kind
Know whether a value is Local, Utc, or Unspecified before converting or using it further.

4. Parse safely
TryParseExact or ParseExact should be used when the format is important. Also consider CultureInfo always.

5. Use ISO 8601
The ISO 8601 standard should be used since the round-trip “O” format will maintain all of the date and time information when serialising.

6. Use TimeZoneInfo
It helps you retrieve time zones, convert values between them, and correctly apply daylight saving time rules.

7. Use DateOnly and TimeOnly
When you only need a date or a clock time, use types that clearly express that intent.

8. Use TimeSpan for durations
It provides a consistent and time-zone-independent way to represent and manipulate elapsed time.

9. Store dates intentionally
When you need an exact moment, use UTC; but, when the business meaning depends on it, keep the offset or time-zone context.

The biggest takeaway?

Different date and time types solve different problems.

Each situation has its own correct type, there’s no single one.

Select the type according to what the value really represents.

Save this post and return to it the next time dates and times start fighting back.

♻️ Repost to help other .NET developers become better at working with dates and times.

➕ Follow me (@pavle_dav), to improve your .NET skills.

⸻⸻⸻

📰 Subscribe to my newsletter at https://t.co/fvaagl7TJ2

[Reza Dorrani @rezadorrani]

🚀 In my latest video, I use the Canvas Apps MCP Server and Flow Agent MCP Server together to build a complete end-to-end solution.

Watch here: https://t.co/H2gqcjyvh7

You’ll also see where MCP works well and how much development time it can save.

[Arun Vinoth (3x MVP) 🇮🇳🇺🇸 @arunvinoth]

LinkedIn post and the conversation around deployment window clash and eventual solution import failures, sweet spot plannings for the next client project 👇🏼

https://t.co/MZ6tjazaPR

@precog_tech

[Burke Holland @burkeholland]

Pro tip:

Tokens are precious.

Run `/chronicle cost-tips` in @GitHub Copilot to get tips on what you're doing that's burning all those precious tokens and how to get more bang for the buck.

[Temmy Wahyu Raharjo @temmy_raharjo]

Just Blogged 📢: SSIS: Auto-Rebuilding SSIS Script Tasks/SSIS Components to Sync Stale References

https://t.co/RB0NyLVv1e

#ssis #microsoft #developers #scripttask #scriptcomponent

[Dave McCollough @davemccollough]

Solid Microsoft reference architecture for Foundry chat.

Friendly reminder: the model is only one part of production AI.. the real work is identity, networking, egress, grounding, state, monitoring, and governance. https://t.co/tgBGDvwp2L

[Temmy Wahyu Raharjo @temmy_raharjo]

Just Blogged 📢: AI-Powered Summaries for Power Platform Solution Changes with GitHub Actions

Create a GitHub action to export and create a summarization while reviewing the changes!

https://t.co/gYIxnEH1Ic

#microsoft #github #ai #cicd #powerplatform #review #dataverse

[Steve Knutson 🇳🇿MVP & RD #SharePoint @nztechtweet]

Download the Skill here: https://t.co/o97Yj6EItZ

[GPS @madebygps]

Microsoft just open-sourced Azure Skills, a set of Azure-specific capabilities that help coding agents deploy, diagnose, monitor, and manage cloud resources.

It includes 25 Azure-focused skills that connect to live Azure context through MCP-backed tools, so your agent can understand what is running, reason about the right next step, and take informed action directly.

Pair it with the GitHub Copilot CLI and you can accomplish Azure tasks right from your terminal with natural language.

Azure Skills: https://t.co/rNDYjHcWx8
GitHub Copilot CLI: https://t.co/p60dxYfsIN

[Josh Cook | Microsoft MVP @FlowAltDelete]

Copilot Cowork SURVIVAL TIP.

Tell Copilot Cowork to create a requirements.md file at the start of your session.

Not later.
At the start.
Have it track:
decisions,
requirements,
open items,
conversation context,
audit notes,
files created.

Then if the session glitches or you need a fresh chat, open the Output folder, copy the OneDrive link, paste it into the new session, and tell Cowork:

Use the files from our previous session.

This has saved me more than once.

Cowork loves creating files.
Make it create the one that keeps your work alive.

Mini blog post link in the comments👇

[Kayla Cinnamon ☕️ @cinnamon_msft]

Don't know when to use custom instructions vs. custom agents. vs agent skills? Check out my latest video! 💫
https://t.co/Eg9GZsSjpm

[GitHub Changelog @GHchangelog]

GitHub Copilot users can now connect to the Figma MCP server to both pull design context into code and send rendered UI to Figma as editable frames.

https://t.co/JVS1BuJ0Pj

[Dr Milan Milanović @milan_milanovic]

A useful repo: Curated Agent Skills for Microsoft & Azure

https://t.co/ds2jLfq0RY

[Thomas Thornton @tamstar1234]

[New Blog Post] Azure Diagram Agent Skill with Drawio MCP

I’ve been experimenting with generating Azure architecture diagrams using Drawio MCP + GitHub Copilot.

In this post I share an Azure Diagram Agent Skill that helps generate diagrams that are consistent, readable, and usable in real architecture reviews.

🔗 https://t.co/MPY8OwP4V6

#Azure #GitHubCopilot #PlatformEngineering #DevOps #CloudArchitecture

[Debbie O'Brien @debs_obrien]

https://t.co/Eu8i22dFco

[Thomas Thornton @tamstar1234]

[New Blog Post] Drawio MCP for Diagram Generation: Why It’s Worth Using

Using GitHub Copilot + https://t.co/t2IrGlPjQE MCP, I generate diagrams from structured input tied to code & infra. Drafts in minutes, refined deliberately, committed to Git.

🔗 https://t.co/U0PjJeq1YE

#PlatformEngineering #DevOps #IaC #GitOps #GitHub #GitHubCopilot