<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Walidchafroud on Medium]]></title>
        <description><![CDATA[Stories by Walidchafroud on Medium]]></description>
        <link>https://medium.com/@walidchafroud?source=rss-1cef04a92e1f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*m-9AklO4GWHGtWeFIeGL1A.jpeg</url>
            <title>Stories by Walidchafroud on Medium</title>
            <link>https://medium.com/@walidchafroud?source=rss-1cef04a92e1f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 01:39:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@walidchafroud/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Power Platform vs Traditional Development: When Should You Use Low-Code?]]></title>
            <link>https://medium.com/@walidchafroud/power-platform-vs-traditional-dev-when-to-use-low-code-99cb60535a7c?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/99cb60535a7c</guid>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[microsoft]]></category>
            <category><![CDATA[low-code]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Mon, 21 Sep 2026 13:54:34 GMT</pubDate>
            <atom:updated>2026-09-21T14:08:21.292Z</atom:updated>
            <content:encoded><![CDATA[<p>Should you build your next business application with Microsoft Power Platform or traditional software development?</p><p>The answer depends on more than technology. Project complexity, development speed, scalability, integration requirements, maintenance, security, and long-term ownership all influence whether low-code or traditional development is the right approach.</p><p>In this guide, we’ll compare <strong>Microsoft Power Platform and traditional development</strong> and look at when to use <strong>Power Apps, Power Automate, Dataverse, or custom code</strong> and why the two approaches can often work together rather than compete.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cSdUcTYi2_-X-zeRA2HvnA.jpeg" /></figure><h3>Power Platform vs. Traditional Dev: When to Use LowCode</h3><p>This question comes up in almost every organization adopting Power Platform, usually framed as a competition: “should we build this in Power Apps or should we hand it to the dev team?” After building solutions on both sides of that line, I think the framing itself is the problem. The real question isn’t which is “better” it’s which fits the specific combination of speed, complexity, scale, and lifecycle your project actually needs.</p><h3>Where lowcode clearly wins</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZRuYJul_hyUOnJ6VVQZAhQ.jpeg" /></figure><p><strong>Timetovalue on internal, departmental tools.</strong> A canvas app connected to a SharePoint list, built and deployed in an afternoon, solving a real problem for twenty people traditional development simply cannot compete with that timeline, and trying to force it to is usually a waste of engineering capacity better spent elsewhere.</p><p><strong>Businessowned logic that changes often.</strong> If the rules of a process (approval thresholds, routing logic, form fields) are going to change quarterly based on business decisions, putting that logic in a Power Automate flow that a business analyst can update themselves beats filing a change request to a dev team every time a threshold shifts.</p><p><strong>Bridging existing Microsoft 365 data.</strong> If your data already lives in SharePoint, Dataverse, or across the Microsoft 365 graph, Power Platform’s native connectors get you to a working solution faster than custom API integration work would, especially for CRUDheavy internal tools.</p><h3>Where traditional development still wins, clearly</h3><p><strong>Highscale, highperformance, or highly custom UX:</strong> Power Apps has real ceilings with tens of thousands of concurrent users, extremely custom UI requirements, or performancecritical rendering (complex data visualizations, realtime gamingstyle interactions), traditional development gives you control that lowcode platforms don’t.</p><p><strong>Deep integration with nonMicrosoft systems at scale:</strong> Power Automate’s connectors cover an enormous surface area, but for complex, highvolume, or highly specific integrations with thirdparty systems, custom code with proper error handling, retry logic, and observability tooling is usually more maintainable longterm.</p><p><strong>Longterm IP and portability concerns:</strong> If your organization’s competitive advantage depends on a specific piece of software logic, building it in a proprietary lowcode platform creates a different kind of technical debt one tied to a specific vendor’s roadmap and licensing model rather than to code you</p><p>fully own and can move anywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7IsvuXcYsWRwNN3vB7uX9w.jpeg" /></figure><h3>The pattern I actually use: a decision framework, not a rule</h3><p>Rather than a binary choice, I evaluate new requests against four questions:</p><p>1 <strong>Who owns the logic longterm?</strong> If it’s the business team, lean lowcode. If it’s core to a product engineering owns, lean traditional dev.</p><p>2 <strong>What’s the expected user scale?</strong> Under a few hundred concurrent users and mostly internal Power Platform handles this comfortably. Publicfacing, hightraffic traditional dev, or Power Pages if it must stay in the Microsoft 365 ecosystem.</p><p>3 <strong>How often will requirements change?</strong> Frequent, businessdriven change favors lowcode’s editability. Rare, stable requirements make either option viable, so pick based on the other factors.</p><p>4 <strong>What’s the actual cost of getting this wrong?</strong> A departmental scheduling app failing gracefully is a minor inconvenience. A customerfacing payment flow failing is a different risk category entirely match your platform choice to your actual risk tolerance, not to what’s trendy.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cJ3U9YpxVk3SK-SnCOfyxw.jpeg" /></figure><h3>What 2026’s AIfirst Power Platform releases change about this calculus</h3><p>This year’s release waves have pushed a lot more capability into lowcode agentic AI, Dataverse APIs, MCP server support, a Python SDK for procode extensibility inside Power Platform itself. The line between “lowcode” and “procode” is blurring on purpose; Microsoft’s own stated goal is shortening the distance between a business need being reported and a working solution existing, and increasingly that means lowcode and procode tooling living inside the same platform rather than being two separate worlds.</p><p>Practically, this means the old advice “start in lowcode, rebuild in procode once you outgrow it” is becoming less absolute. More organizations are finding they can extend a Power Platform solution with real code (via the new SDKs and APIs) instead of doing a full rewrite, which changes the calculus toward “start lowcode more often, since the exit ramp to procode is less of a cliff than it used to be.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pt2RhugmViC-okHZoetsww.jpeg" /></figure><h3>My honest take</h3><p>I don’t think this is a debate with a permanent winner, and I’d be skeptical of anyone on either side</p><p>who tells you it is. The organizations getting the most value right now are the ones treating Power Platform and traditional development as complementary tools in the same toolbox, chosen deliberately per project rather than defended as an ideology. If you’re the person making this call, write down your actual answers to the four questions above before your next project kickoff it’s a better use of ten minutes than any framework debate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=99cb60535a7c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding Microsoft Power Platform Architecture]]></title>
            <link>https://medium.com/@walidchafroud/understanding-microsoft-power-platform-architecture-7bb5e756d7f7?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7bb5e756d7f7</guid>
            <category><![CDATA[power-bi]]></category>
            <category><![CDATA[powerapps]]></category>
            <category><![CDATA[power-automate]]></category>
            <category><![CDATA[microsoft-power-pages]]></category>
            <category><![CDATA[copilot-studio]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Wed, 02 Sep 2026 15:41:49 GMT</pubDate>
            <atom:updated>2026-09-02T15:41:49.901Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Rkuj1s9q3IJ68QTkLhpd8Q.png" /></figure><p><strong>Microsoft Power Platform</strong> is often introduced one tool at a time first Power Apps, then Power Automate, then Power BI and that approach makes it easy to miss the bigger picture: <br>these tools aren’t separate products bolted together, they’re a connected system built around a shared data layer. This guide walks through that system visually, using architecture diagrams that show how the pieces actually fit.</p><h3>1. The Power Platform at a Glance</h3><p>Before diving into architecture, it helps to see the full family of tools in one place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/638/1*y0TKV01Wrm3PbZL02YxFgQ.jpeg" /><figcaption><em>Figure 1.The Power Platform family of tools, centered on Dataverse</em></figcaption></figure><p>At the center sits Dataverse, the common data platform that almost everything else reads from or writes to. Around it:</p><p>• <strong>Power Apps </strong>give you two app models Canvas apps (and Pages, their newer building block) for pixel perfect, drag-and-drop design, and Model-driven apps for apps generated directly from your data structure.</p><p>• <strong>Power Automate </strong>covers automation in several flavors: automated cloud flows (trigger-based), instant cloud flows (manually triggered), scheduled cloud flows (time-based), and desktop flows for RPA on local machines plus business process flows and workflows for guiding structured processes.</p><p>• <strong>Power Pages </strong>builds external-facing websites whose configuration and business data live in Dataverse.</p><p>• <strong>AI Builder </strong>adds AI models into your apps and flows and notably, it requires a Dataverse database to function.</p><p>• <strong>Copilot Studio and Power BI </strong>round things out for conversational AI and analytics.</p><p>The key takeaway from this diagram: everything inside the dashed boundary depends on being stored in an environment with Dataverse. That boundary is the architectural backbone of the whole platform.</p><h3>2. Why Dataverse Is the Hub, Not Just Another Data Source</h3><p>Zooming into Dataverse itself makes its role clearer it isn’t just a database option, it’s the integration point that lets every tool talk to every other tool.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1021/1*2XyKfWBBbG0pq9B_0Fosrg.jpeg" /><figcaption><em>Figure 2. Dataverse as the connective hub between apps, automation, analytics, and data sources.</em></figcaption></figure><p>Reading this diagram clockwise:</p><p>• <strong>Power Apps </strong>lets you interact with the data sitting in Dataverse.</p><p>• <strong>Power Automate </strong>lets you act on the data running processes whenever records change.</p><p>• <strong>Power BI </strong>lets you interpret the data turning it into reports and dashboards.</p><p>• <strong>Power Virtual Agents </strong>(now part of Copilot Studio) lets end users interact with that data conversationally.</p><p>Feeding into Dataverse on the left, data connectors and Azure Data Factory pull in data from on-premises systems, cloud data, and SaaS applications. Underneath, Dataverse can also draw on semi-structured data, relational databases, and Azure Data Lake Storage Gen2. On the right, an integration layer pushes data out through Event Hub, webhooks, SQL exports, or ADLS meaning Dataverse isn’t a closed box; it’s a two-way bridge between your low-code apps and the rest of your enterprise systems.</p><h3>3. Scaling Up: The Full Enterprise Architecture</h3><p>Once a Power Platform solution grows past a single app, it typically starts pulling in genuine enterprise infrastructure security, orchestration, and external data. This is what that looks like in practice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*S2DhDsv19-m5VqeQuYxmZw.jpeg" /><figcaption><em>Figure 3. An enterprise-grade Power Platform architecture with storage, security, and orchestration layers</em></figcaption></figure><p>A few things stand out in a production-grade setup like this:</p><p>• <strong>Storage </strong>splits across Blob storage and Azure SQL database, both feeding into Dataverse useful when you have data volumes or types that don’t belong in Dataverse itself.</p><p>• <strong>Azure Key Vault </strong>sits alongside Dataverse to protect secrets, connection strings, and credentials rather than storing them in flows or apps directly.</p><p>• <strong>Orchestration </strong>is handled by Data Factory (for bulk data movement) and Power Automate (for process automation), both governed centrally by Microsoft Entra for identity and access.</p><p>• <strong>Microsoft 365 </strong>SharePoint, Outlook, Teams, and Forms connects directly into this architecture, which is why Power Platform solutions so often start life as “just automate this Teams/SharePoint process.”</p><p>• <strong>Third-party APIs </strong>connect in from the outside, usually via Blob storage or custom connectors, rather than touching Dataverse directly.</p><p>• <strong>Power Apps and Power BI, at the top, </strong>remain the consumption layer what actual users interact with.</p><p>This is essentially the same core loop as the simpler diagram above (Apps → Dataverse → Automate → BI), just with the identity, security, and integration plumbing made explicit.</p><h3>4. The Same Architecture, Reframed</h3><p>Here’s a cleaner, more presentation-friendly version of the same concept useful when you’re explaining Power Platform to stakeholders who don’t need the full technical detail.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3PL_yXmxIyVOSO5lufB5GA.jpeg" /><figcaption><em>Figure 4. Power Platform architecture grouped by data sources, processing core, and outputs.</em></figcaption></figure><p>This view groups things by role rather than by product:</p><p>• <strong>Data Sources </strong>on the left SharePoint, Outlook, Teams, external systems like Xero, HubSpot, and Salesforce, plus traditional databases and APIs.</p><p>• <strong>The processing core </strong>in the middle Power Apps for building custom business applications, Power Automate for workflow automation, and Power BI for analytics all wired through Dataverse as the common data platform.</p><p>• <strong>Outputs </strong>on the right the actual deliverables: web apps, mobile apps, automated workflows, real-time dashboards, and notifications.</p><p>It’s the same story told three times now, at increasing levels of detail which is deliberate. If you only remember one thing about Power Platform architecture, it should be this: data flows in, Dataverse holds it, the three core tools act on it, and value flows back out.</p><h3>5. Two App Models: Canvas vs. Model-Driven</h3><p>Power Apps itself isn’t one thing it’s two different ways of building an app, and the architecture diagram makes the distinction obvious.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9bI5slrfp9LY-RVuJ9dYAQ.jpeg" /><figcaption><em>Figure 5. Model-driven app architecture: the app is generated from the Dataverse schema</em></figcaption></figure><p>A model-driven app is essentially generated from your Dataverse schema. You configure the database structure in Solution Explorer, configure the app’s views and forms in the Editor, and the app itself is largely assembled automatically mobile and web users just access and browse the result. This is the right choice when your app should closely mirror well-structured, relational business data (case management, inventory, CRM-style apps).</p><p>A canvas app, by contrast, is built the opposite way you design the interface first, pixel by pixel, and connect it to data afterward. That’s the model you see in the Power Apps Studio itself:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iW78kootCq9gjlnDV8Jdnw.jpeg" /><figcaption><em>Figure 6. The Power Apps Canvas Studio, with its main functional zones labeled.</em></figcaption></figure><p>This is the actual working environment, broken into its functional zones:</p><p>1. <strong>Ribbon </strong>Home, Insert, View, Action, and Settings menus for building and configuring the app.</p><p>2. <strong>Top-right toolbar </strong>save, undo/redo, run/preview, and collaboration/help tools.</p><p>3. <strong>Left navigation rail </strong>switches between Tree view, Insert, Data, Media, Power Automate, Advanced tools, and Search.</p><p>4. <strong>Insert panel </strong>the component library: labels, forms, inputs, galleries, and layout elements.</p><p>5. <strong>Collapsed rail </strong>same rail, showing the icon-only collapsed state.</p><p>6. <strong>Canvas </strong>the actual design surface where you place and arrange controls.</p><p>7. <strong>Properties panel </strong>Fill, background image, and other settings for whatever’s selected.</p><p>8. <strong>Zoom controls </strong>for adjusting your view of the canvas.</p><p>And here’s that same Insert panel in use, with Edit form selected the control you’d use to bind a screen directly to a Dataverse table or other data source without hand-building every input field:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WIfVBT3rAGxgR4o1-E3mAQ.jpeg" /><figcaption><em>Figure 7. Inserting an Edit form bound to a data source in a canvas app.</em></figcaption></figure><p>This single screenshot ties the whole guide together: a canvas app, built visually, being connected to structured data which is exactly the relationship the very first diagram described between “Canvas app / Page / Model-driven app” and “Dataverse.”</p><h3>Putting It All Together</h3><p>Whether you’re looking at the simplest overview or the full enterprise diagram with Key Vault and Data Factory, the underlying pattern never changes:</p><p>1. Data comes from somewhere (Microsoft 365, external systems, databases, APIs).</p><p>2. Dataverse stores and governs it centrally.</p><p>3. Power Apps, Power Automate, Power BI, and Copilot Studio each provide a different way to interact with that data.</p><p>4. Security and identity (Entra, Key Vault) and orchestration (Data Factory) hold the whole thing together as it scales.</p><p>Once that mental model clicks, every individual feature an Edit form, a cloud flow trigger, an AI Builder model stops looking like an isolated tool and starts looking like exactly what it is: one more way of touching the same shared data platform.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7bb5e756d7f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft 365 Copilot in Power Apps: Public Preview Walkthrough]]></title>
            <link>https://medium.com/@walidchafroud/microsoft-365-copilot-in-power-apps-public-preview-walkthrough-bc766f1bff14?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/bc766f1bff14</guid>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[walkthrough]]></category>
            <category><![CDATA[powerapps]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 09:03:02 GMT</pubDate>
            <atom:updated>2026-08-14T09:03:02.628Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kBFErRegbi48M3UVMsMsLw.jpeg" /></figure><p><strong>Microsoft </strong>is bringing Power Apps directly into Microsoft 365 Copilot, and the public preview gives a clear picture of where this is headed.<br>your model-driven apps aren’t just something users open separately anymore they’re becoming something Copilot can surface, query, and even act on conversationally, from inside the flow of everyday Microsoft 365 work.</p><h3>What’s actually in preview right now</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*sjmwyNNnxiri7BIP.png" /></figure><p>The centerpiece of this preview is <strong>conversational access to model-driven app data through Grids and Forms</strong>, with Custom Tools support coming afterward. <br>In practical terms: instead of a user opening an app, navigating to a view, filtering a grid, and manually reading through records, they can ask Copilot Chat a question and get an answer pulled directly from that app’s underlying Grids and Forms while still being able to jump into the actual app UI when they need the full context. <br>Microsoft frames this as bringing “app-powered UI experiences” into Microsoft 365 Copilot conversations, which is a meaningful distinction from just connecting Copilot to your data generically. The app’s existing structure — its views, its forms, its business logic — becomes something Copilot can respect and use, rather than Copilot having to reconstruct that understanding from raw Dataverse tables</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dNOJze5pGjBL_ap1.jpg" /></figure><h3>Why this matters more than it might first appear</h3><p>Most organizations already invested heavily in building model-driven apps with carefully designed grids, forms, and business rules. <br>The risk with generic AI chat layered on top of business data has always been that it bypasses all that carefully built structure a chatbot that ignores your validation rules and view logic is a governance headache waiting to happen. <br>This preview takes a different approach: <strong>Copilot chat inside apps</strong> has context of what a user is doing within the app itself, and the broader Microsoft 365 Copilot integration extends that same principle outward respecting the app’s existing forms and grids rather than working around them</p><h3>What to expect as this moves toward general availability</h3><p>Based on the pattern Microsoft has followed with similar previews (<strong>Copilot </strong>in <strong>SharePoint </strong>followed a comparable path preview, then default-on rollout), expect :</p><ul><li><strong>Custom Tools</strong> to expand what Copilot can *<strong>do</strong>* inside an app-powered conversation, not just what it can *<strong>show</strong>* likely enabling users to trigger actions (create a record, update a status) conversationally rather than only querying</li><li><strong>Governance and DLP policies</strong> to matter a lot here if your Power Platform environment has connector restrictions or data loss prevention policies in place, those need to extend cleanly to this new conversational surface, or you’ll create a policy gap</li><li><strong>Admin visibility tooling</strong> (similar to the SharePoint Agent Access Insights heatmap Microsoft has been rolling out) to likely follow, since “what is Copilot doing with my app’s data” is exactly the kind of question admins will start asking</li></ul><h3>What makers should do now, during preview</h3><ol><li><strong>Audit your forms and grids for AI-readiness :</strong>If your model-driven app’s forms have cryptic field names, missing descriptions, or inconsistent structure, Copilot’s conversational answers will inherit that mess. Clean, well-labeled forms translate directly into better conversational responses.</li><li><strong>Review DLP policies against this new surface :</strong><br> Don’t assume your existing connector-level DLP automatically covers a conversational access pattern validate it explicitly once this rolls out to your tenant.</li><li><strong>Identify a pilot app:<br></strong> Rather than waiting for GA and turning this on tenant-wide, pick one well-maintained app with a real business owner and test the conversational experience there first. You’ll learn more from one good pilot than from reading ten more articles about this feature (including this one)</li></ol><h3>My take</h3><p>This is part of a consistent direction across Microsoft’s 2026 roadmap: <strong>apps</strong>, <strong>Copilot</strong>, and <strong>Dynamics </strong>are all being pulled into the same conversational <strong>fabric </strong>rather than staying as separate destinations users have to remember to visit. <br>For makers, the actionable takeaway isn’t :</p><blockquote>“wait and see it’s make sure the app you already built is clean enough that when Copilot starts talking about it, it says something useful.”</blockquote><blockquote><em>Source: Microsoft Power Platform Blog, Power Apps product updates.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kkt1l51G544qJe8zoFxXNw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bc766f1bff14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SharePoint + Copilot: What Changed in the Last Update]]></title>
            <link>https://medium.com/@walidchafroud/sharepoint-copilot-what-changed-in-the-last-update-561f65833181?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/561f65833181</guid>
            <category><![CDATA[copliot]]></category>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[news]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Tue, 04 Aug 2026 12:52:30 GMT</pubDate>
            <atom:updated>2026-08-04T13:51:45.313Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQqu6xPygY7Xuee5ZiBVZA.png" /></figure><p>Copilot in SharePoint has moved fast this year, but the July 2026 update is arguably the biggest shift yet: it turns the Copilot chat pane from a “helpful Q&amp;A assistant” into something closer to an active operator that can build files, reorganize your content, and automate workflows all from natural language, right inside the site you’re already working in</p><h3>The headline change: on by default</h3><p>Since June 16, 2026, Copilot in SharePoint has been rolling out on by default for everyone holding a Microsoft 365 Copilot license. If you’re an admin, this matters: you no longer need to explicitly enable it per site, which means your governance and content-hygiene work needs to happen *before* your users start prompting Copilot against messy libraries, not after</p><h3>What’s new in the July update</h3><p><strong>Generate Office files straight from site content :</strong> Ask Copilot to create a Word document, Excel workbook, or PowerPoint deck based on what’s already sitting in a SharePoint site pages, lists, or documents. Instead of starting from a blank file and manually pulling data together, a program manager can turn a project site’s notes into a first-draft status deck in minutes. No copy-pasting between apps required.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*5j9haFO0IcuXhbpz" /></figure><p><strong>Skills discovery :</strong> Copilot now surfaces a /Skills menu reusable, site-specific automations that capture your team’s repeatable processes (document guidelines, review checklists, summarization templates) so they don’t get reinvented every time. You can also ask Copilot to help you *build* new skills, including generating a starter SharePoint file for a site, which effectively documents your site’s structure and conventions in a format Copilot itself can reference later.</p><p><strong>Conversational library management :</strong> You can now ask Copilot to reorganize files and folders, and even build interactive HTML dashboards from list data all through chat rather than clicking through the UI. <br>Early hands-on reviews describe this as genuinely functional, not just a demo trick, though with the expected rough edges of any brand-new capability. Direct sharing from chat. Ask Copilot to share a specific file with a specific person while you’re mid-conversation no more breaking flow to hunt down the sharing dialog</p><h3>Why this matters beyond the feature list</h3><p>The pattern across the last several months of Copilot-in-SharePoint updates (Knowledge Agent fi rebranded as “AI in SharePoint” back in March, now this July operator-mode update) shows Microsoft steadily collapsing the distance between “content lives in SharePoint” and “work gets done from SharePoint.” <br>That’s a real productivity story, but it raises the stakes on information architecture: Copilot’s accuracy and usefulness depend heavily on how well your libraries, metadata, and permissions are structured messy sites now produce messy AI output faster than ever, at scale.</p><h3>What SharePoint admins should do this week</h3><p><strong><em>Audit authoritative sources :</em></strong> Admins can now designate specific SharePoint sites as authoritative content in the Microsoft 365 admin center, which improves how those sites rank in Copilot search results. <br>If you haven’t done this, your most trustworthy sites may be getting outranked by outdated ones.</p><p><strong><em>Check the new Agent Access Insights heatmap</em></strong> : if you’re on a plan that includes it it visually flags unusual AI-agent access patterns across sites, which is becoming essential now that agents (not just humans) are querying your content.</p><p><strong><em>Clean up before you scale :</em></strong> Since Copilot is now default-on, any library with duplicate, outdated, or poorly-tagged files will surface that mess directly in generated documents and dashboards. This is the moment to do the metadata cleanup you’ve been postponing</p><h3>My take</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r8DEWbV3zjHvmt2OFagySA.png" /></figure><p>This update is a genuine step-change, not an incremental tweak but “on by default” combined with “operator-mode automation” means the organizations that benefit most will be the ones who treated SharePoint governance seriously *before* this rolled out. <br>If that’s not you yet, start with authoritative sources and a metadata pass this week it’s the highest-leverage 30 minutes you can spend before your users start relying on Copilot-generated content in front of leadership</p><blockquote>Sources: Microsoft 365 Copilot Community Hub release notes, March–July 2026.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=561f65833181" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What’s New in Power Apps : 2026 Release Wave 1]]></title>
            <link>https://medium.com/@walidchafroud/whats-new-in-power-apps-2026-release-wave-1-58819c2286ac?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/58819c2286ac</guid>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[microsoft-power-platform]]></category>
            <category><![CDATA[microsoft-power-automate]]></category>
            <category><![CDATA[powerapps]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 13:12:18 GMT</pubDate>
            <atom:updated>2026-07-22T13:12:18.026Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_njswLO9cszh4cFJvJrejg.png" /></figure><p><strong>What’s New in Power Apps</strong></p><p>If you build with Power Apps, this is the release wave to pay attention to. Microsoft’s 2026 release wave 1 rolls out between April and September 2026, and it’s less an incremental update than a genuine shift in how apps get built and how they behave once they’re live. Here’s what actually matters, without the marketing fluff.</p><h3><strong>The big theme: AI is no longer a bolt-on</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*5PukZkri90T2u7Jsvka8OA.jpeg" /></figure><p>In previous waves, AI features felt like extras layered on top of the “real” app. This wave treats AI as core infrastructure. Copilot now lives <em>inside</em> model-driven apps with full context of what the user is doing not a separate chat window bolted to the side, but something that understands the record you’re looking at and can act on it.</p><p>Pair that with <strong>Work IQ</strong> integration, which gives Copilot contextual access to your organization’s emails, meetings, Teams messages, and documents, and you get an assistant that actually knows your business instead of answering generically.</p><p>For makers, this means fewer custom integrations to wire up “smart” behavior into your apps a lot of it is becoming a platform capability you just turn on.</p><h3><strong>Modern look becomes the default</strong></h3><p>Model-driven apps are getting a refreshed, consistent UI, and importantly this modern look is becoming the <em>default</em> rather than an opt-in preview. The streamlined header and navigation are moving to general availability. If your organization has apps that still look like classic Dynamics from five years ago, this wave is your natural trigger point to modernize.</p><p><strong>What to check:</strong></p><p>if you’re an admin, review which apps will automatically pick up the modern theming versus which features need manual enabling Microsoft splits this clearly in the release plan, and it’s worth ten minutes to avoid surprising your users.</p><h3><strong>Canvas apps: mobile and offline get real investment</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dbrs3hgBK3p4iSnfMWGJHw.png" /></figure><p>Canvas apps are getting meaningful mobile productivity and offline resilience improvements. If you’ve ever built a canvas app for field workersi nspectors, technicians, sales reps you know offline mode has historically been the weak link. This wave brings real-time Dataverse support designed specifically for offline-first scenarios, along with quality improvements across commonly used modern controls (<strong>Combo Box, Text Input, Date Picker, and others</strong>).</p><h3><strong>Agents are becoming a first-class citizen</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/1*NZWm5jDjIBxzQ3NcUuz-1w.png" /></figure><p>Power Apps is leaning hard into agentic AI. You can now build agents from existing apps and deploy them to handle work autonomously, with tooling to monitor agent activity and troubleshoot when an agent gets stuck. There’s also a new <strong>Agent Feed</strong> essentially a supervision inbox that categorizes what your agents are doing into “Completed” and “Needs Attention,” so a human stays in the loop without babysitting every automated action.</p><p>For pro developers, agent programmability is expanding too <strong>Dataverse APIs</strong>, <strong>MCP server support</strong>, and a <strong>Python SDK</strong> are all part of this wave, which signals Microsoft wants Power Platform agents to be extensible well beyond low-code scenarios.</p><h3><strong>Governance gets real teeth</strong></h3><p>If you’re the person who has to answer for what Power Platform is doing across your tenant, this wave gives you more to work with: admin controls for agent security, real-time risk assessment in Copilot Studio, and AI-powered governance agents that can automate tenant monitoring and even remediation. There’s also better visibility into Copilot credit consumption with pay-as-you-go caps, which matters a lot once AI usage becomes metered and budgets start getting real scrutiny.</p><h3><strong>My take</strong></h3><p>The pattern across this wave is consistent: Microsoft is betting that the gap between “someone reports a business problem” and “a working solution exists” should keep shrinking, and AI is the lever doing most of that shrinking. If you’re a maker, don’t just wait for these features to show up go look at what’s flagged for “Users, automatically” versus what needs admin enablement in the official release plan, because the surprises usually come from features nobody turned on intentionally.</p><blockquote>Sources: Microsoft Learn release plan documentation for Power Apps and Power Platform, 2026 release wave 1.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=58819c2286ac" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vers un système de santé intelligent : le rôle clé des données unifiées, sécurisées et du cloud]]></title>
            <link>https://medium.com/@walidchafroud/vers-un-syst%C3%A8me-de-sant%C3%A9-intelligent-le-r%C3%B4le-cl%C3%A9-des-donn%C3%A9es-unifi%C3%A9es-s%C3%A9curis%C3%A9es-et-du-cloud-a1d1014dbd71?source=rss-1cef04a92e1f------2</link>
            <guid isPermaLink="false">https://medium.com/p/a1d1014dbd71</guid>
            <category><![CDATA[healthcare-technology]]></category>
            <category><![CDATA[security]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[microsoft-copilot]]></category>
            <category><![CDATA[healthcare]]></category>
            <dc:creator><![CDATA[Walidchafroud]]></dc:creator>
            <pubDate>Wed, 06 May 2026 09:31:57 GMT</pubDate>
            <atom:updated>2026-05-06T09:31:57.147Z</atom:updated>
            <content:encoded><![CDATA[<p>Dans l’écosystème complexe de la santé numérique, l’interopérabilité n’est plus un simple défi technique, mais le catalyseur indispensable d’un système de soins basé sur la valeur .Historiquement, la fragmentation des données entre les dossiers patients informatisés , l’imagerie médicale et les systèmes de facturation a créé des silos étanches, freinant l’innovation et la sécurité des soins.<br> L’objectif de ce rapport est d’analyser la convergence stratégique entre le standard FHIR (Fast Healthcare Interoperability Resources), les cadres réglementaires de protection des données ( RGPD et HIPAA ) et les plateformes d’IA de pointe de Microsoft ( Fabric , Foundry , Copilot ).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3A5pkoVk-__Gs7aa4wltpQ.png" /></figure><h3><strong>1. L’Unification des Données Patients : Vers un Dossier Longitudinal Complet :</strong></h3><p>La fragmentation des données patient est un défi majeur dans le secteur de la santé. Les informations sont souvent dispersées entre différents systèmes, hôpitaux, cliniques et dispositifs portables, rendant difficile l’obtention d’une vue d’ensemble cohérente de l’état de santé d’un individu. Le concept de dossier patient longitudinal (Longitudinal Patient Record) vise à agréger toutes ces données en un point unique et accessible. Microsoft Cloud for Healthcare, par exemple, est conçu pour unifier les données provenant de sources disparates, incluant les dossiers médicaux électroniques (DME), les dispositifs portables et l’imagerie médicale . Cette unification est cruciale pour permettre aux professionnels de la santé de prendre des décisions éclairées, basées sur une compréhension holistique du parcours de soins du patient.</p><h3>2. L’interopérabilité : un pont entre les systèmes</h3><p>L’interopérabilité est la capacité des différents systèmes et applications à échanger et interpréter les données de manière transparente. Le standard FHIR (Fast Healthcare Interoperability Resources) est devenu la pierre angulaire de cette interopérabilité dans le domaine de la santé. Microsoft Azure joue un rôle prépondérant en offrant des services tels que l’Azure API for FHIR, un service managé qui facilite l’échange rapide et sécurisé de données de santé conformes à la norme FHIR . Ces APIs permettent non seulement d’intégrer les systèmes existants, comme Epic ou Cerner, mais aussi de développer de nouvelles applications qui peuvent accéder et partager des informations de manière standardisée, brisant ainsi les silos de données et favorisant une collaboration accrue entre les acteurs de la santé .</p><p><strong>Microsoft décline le support FHIR à travers deux offres distinctes :</strong></p><p>- <strong>Azure API for FHIR</strong> : Service managé hautement sécurisé, principalement axé sur la version R4 pour répondre aux exigences de production et de conformité actuelles.</p><ul><li>Serveur Open-source (<strong>FHIR Server for Azure</strong>) : Implémentation extensible supportant les versions STU3, R4, et R5 (actuellement en bêta) . Il offre une flexibilité de stockage via Azure Cosmos DB ou Azure SQL.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XlE1rZjVAaGd2nmnAVm0Ng.png" /></figure><h3>3. Capacités d’Intelligence Artificielle Intégrées : L’Ère de la Médecine Prédictive</h3><p>L’intégration de l’intelligence artificielle (IA) et de l’analyse avancée est la pierre angulaire d’un système de santé intelligent. Des plateformes comme Azure Health Data Services de Microsoft offrent une suite d’outils spécifiquement conçus pour gérer les informations de santé protégées (PHI) dans le cloud, tout en respectant les standards ouverts comme <strong>FHIR </strong>et<strong> DICOM</strong> .</p><p>Ces services permettent de combiner des ensembles de données de santé disparates et de les standardiser, ouvrant la voie à des capacités d’analyse avancées. Grâce à des connecteurs avec des outils tels qu’Azure Synapse Analytics, Azure Machine Learning et Power BI, les professionnels de santé peuvent générer des informations précieuses à partir de données du monde réel. Les applications de l’IA sont vastes : aide au diagnostic, optimisation des parcours de soins, identification de cohortes pour la recherche clinique, suivi à distance des patients via des dispositifs connectés, et même la dé-identification des données pour des usages secondaires en recherche . L’IA peut ainsi transformer des données brutes en connaissances exploitables, améliorant l’efficacité et la qualité des soins.</p><h3>4. Sécurité et Conformité : La Confiance au Cœur du Système</h3><p>La gestion des données de santé, particulièrement sensibles, exige une sécurité et une conformité irréprochables. Un système de santé intelligent doit être bâti sur une infrastructure cloud qui adhère aux standards internationaux les plus stricts. Parmi ceux-ci figurent le HIPAA (Health Insurance Portability and Accountability Act) aux États-Unis, le <strong>RGPD </strong>(Règlement Général sur la Protection des Données) en Europe, et des certifications comme <strong>HITRUST CSF</strong> .</p><p>La sécurité est assurée par des mécanismes robustes, incluant le chiffrement des données au repos et en transit, des contrôles d’accès basés sur les rôles (<strong>RBAC</strong>) pour garantir que seules les personnes autorisées accèdent aux informations, et une surveillance continue des systèmes pour détecter et prévenir les menaces. L’<strong>IA</strong> elle-même joue un rôle croissant dans la sécurité, notamment pour la détection d’anomalies et la protection proactive contre les cybermenaces .</p><p>Les fournisseurs de services cloud Microsoft investissent massivement dans la cybersécurité, avec plus d’un milliard de dollars annuels dédiés à la recherche et au développement, et emploient des milliers d’experts en sécurité pour protéger les données de leurs clients . Cette approche multicouche est essentielle pour bâtir la confiance nécessaire à l’adoption généralisée des systèmes de santé intelligents.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_7xVmPWB0KBw-qEr6tNBPA.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a1d1014dbd71" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>