Goloknath

The New Power Apps: Generative Power Meets Enterprise-Grade Trust

This update marks the transition of Power Apps from a “low-code” tool to a “Generative-First” platform. It introduces a reimagined authoring experience where AI agents collaborate with humans to build, refine, and maintain applications.

Real-time User Journey: “Vibe-Coding” an App

The new user journey replaces manual drag-and-drop with a conversational, iterative process known as “vibe-coding”:

Ideation: A business user types a high-level goal: “I want an app to manage our retail store’s inventory and notify me when stock is low.”
Architectural Blueprint: The Power Apps Design Agent instantly drafts the full app structure—proposing a data schema, user roles, and screen layouts.
Real-time Refinement: The user looks at the draft and says, “Add a barcode scanner and change the theme to match our brand colors.” The agent updates the app’s code and UI in real-time.
Agentic Assistance: The maker adds an Agent Feed into the app. Now, when a store manager uses the app, they can ask the built-in agent, “Which items should I reorder based on last month’s trend?”
Trust Validation: Before publishing, the Governance Agent scans the app to ensure it follows company data policies and security standards.

Step-by-Step: How to Enable the New Experience

The “New Power Apps” experience is rolled out through the updated web portal and managed environments:

Step 1: Access the New Portal: Navigate to the specialized entry point (announced as vibe.powerapps.com or accessible via the “Try the new Power Apps” toggle in the standard maker portal).
Step 4: Enable Managed Environments: This feature requires the environment to be “Managed.” Go to the Power Platform Admin Center, select your environment, and click Enable Managed Environments.
Step 3: Toggle Generative Features: Under Environment Settings, ensure “Copilot for makers” and “Generative AI (preview)” are set to On.
Step 4: Use the Design Agent: On the home screen, select “Start with a Plan.” This initiates the multi-agent builder that walks you through the data and UI generation.
Step 5: Add Agentic Components: Within the app designer, insert the “Agent Feed” control from the insert pane to enable human-agent collaboration within the published app.

Infographic: Legacy vs. The New Power Apps

This shift represents the biggest change to the platform since its inception:

Feature	Legacy Power Apps	The New Power Apps
Creation Method	Manual UI & logic building.	Generative Plans & Vibe-Coding.
User Experience	Static forms and galleries.	Agent Feed (Interactive AI assistance).
Data Interaction	Manual Filter/Search queries.	Natural Language Reasoning over data.
Developer Tools	Expression language (Power Fx).	Multi-Agent Collaboration (AI handles the Fx).
Governance	Reactive (post-build audits).	Proactive (AI-guided security guardrails).

References

Introducing the new Power Apps: Generative power meets enterprise-grade trust

Uncategorized

2025 release wave 2 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Role-based Microsoft Copilot offerings

July 20, 2025May 3, 2026 Goloknath

2025 release wave 2 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Role-based Microsoft Copilot offerings (A roadmap for new capabilities slated for release between October 2025 and March 2026).

Real-time User Journey: The AI Agent Partnership

The theme of this release is the transition from AI assistants to AI Agents that act as proactive partners. Here is a journey for a Sales Professional using these new features:

Proactive Research: An AI agent autonomously researches a new lead, gathering public company data and recent news, then creates a prioritized “To-do” item for the seller in Dynamics 365 Sales.
Strategic Engagement: As the seller opens the lead, Copilot delivers actionable insights and identifies “emergent deal risks” (e.g., a competitor’s recent activity) in the flow of work.
Autonomous Operations: While the seller focuses on the client relationship, a Supplier Communications Agent (in Supply Chain Management) automatically coordinates with vendors to ensure the inventory needed for the potential deal is available.
Closing the Deal: Copilot assists in drafting a personalized proposal based on the agent’s research. Once signed, the Finance Agent automatically initiates the reconciliation and analysis process to speed up the financial close.
Supervisor Oversight: The sales manager uses the new Agent Feed in Power Apps to supervise the work of these agents, ensuring quality and accuracy across the team’s automated tasks.

Step-by-Step: How to Enable These Features (Early Access)

Microsoft allows organizations to test these features before they hit production.

Step 1: Check the Release Planner

Visit the Microsoft Release Planner (waverocket.microsoft.com) to create a personalized plan and see exactly when specific features will land in your region.

Step 2: Access Non-Production Environment

Step 3: Enable Early Access (Starting August 4, 2025)

Navigate to Environments > [Your Environment] > Settings > Updates. Look for the “2025 release wave 2” card and select Update now.

Step 4: Validate User Experience

Test the reimagined interfaces in Dynamics 365 Sales or the new Mobile Point-of-Sale in Commerce to ensure they align with your business processes.

Step 5: Configure Autonomous Agents

Go to Microsoft Copilot Studio. Use the new simplified agent creation tools to build a “Team of Agents” that work together across Microsoft 365 and Dataverse.

Step 6: Monitor in Automation Center

Use the new Automation Center in the Power Platform admin center to govern and observe the performance of your new AI agents.

Infographic: Release Wave 2 Highlights by Role

Role / Product	Key Innovation	Business Impact
Sales	AI agents for lead research & deal risk.	Close deals faster with proactive insights.
Service	Agentic case & knowledge management.	Automate service journeys across voice & digital.
Finance	AI-driven reconciliation & financial close agents.	Faster financial close and optimized operations.
Supply Chain	Supplier Communications Agent.	Automate vendor interactions and demand planning.
Human Resources	Guided onboarding agents.	Streamline hire-to-retire with automation.
Power Platform	Human-agent collaboration (Agent Feed).	Supervise AI work with transparency and governance.

References

2025 release wave 2 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Role-based Microsoft Copilot offerings

Uncategorized

2025 Release Wave 2: Transitioning to Proactive, Agent-Based AI Ecosystems

July 19, 2025May 3, 2026 Goloknath

2025 Release Wave 2: Transitioning to Proactive, Agent-Based AI Ecosystems The core theme of this release (covering October 2025 to March 2026) is the shift from “Assistive AI” (waiting for user prompts) to “Agentic AI”—autonomous agents that act as proactive partners to drive business outcomes across Sales, Service, Finance, and Supply Chain.

Real-time User Journey: The Autonomous Supplier Communications Agent

A flagship journey introduced in this wave involves the Supplier Communications Agent within Dynamics 365 Supply Chain Management:

Detection: The agent monitors inventory levels and identifies a potential stockout for a critical component due to a sudden demand spike.
Autonomous Outreach: Without human intervention, the agent drafts and sends an inquiry to preferred vendors to check for lead times and pricing.
Negotiation: The agent receives vendor replies, compares them against historical data and budget constraints, and identifies the best option.
Drafting for Approval: The agent presents a “prepared action” to the Procurement Manager: “I’ve found three vendors who can fulfill this; Vendor X is the cheapest and fastest. Click ‘Approve’ to issue the PO.”
Closing the Loop: Once approved, the agent handles the order entry and updates the demand forecast automatically.

Step-by-Step: How to Enable Wave 2 Features

Microsoft has modernized the rollout process by replacing the legacy “Early Access” toggle with a streamlined “Release Channel” system:

Step 1: Access Admin Center: Log into the Power Platform Admin Center (admin.powerapps.com).
Step 2: Create a Sandbox: It is highly recommended to create a copy of your production environment for testing before enabling new features.
Step 3: Switch Release Channel: Navigate to Environments > [Your Environment] > Settings > Product > Behavior.
Step 4: Opt-in to Monthly Channel: Change the “Release channel” setting to “Monthly channel”. This immediately enables the Wave 2 preview features for your environment.
Step 5: Configure Specific Agents: For features like the Sales Research Agent or Finance Reconciliation Agent, go into the respective app settings (e.g., Copilot Studio) to ground the agent in your specific Dataverse tables.

Infographic: 2025 Wave 2 Strategic Pillars

This release wave focuses on four key pillars of the “Agentic Era”:

Pillar	Feature Highlight	Impact
Agentic Power Apps	Agent Feed	A hub for humans to supervise and interact with multiple agents working in the background.
Autonomous ERP	Payables & Sales Agents	Moves Business Central from manual entry to automated order-taking and payment reconciliation.
Intelligent Portals	Power Pages Security Agent	Proactively scans external-facing sites for vulnerabilities and suggests fixes to makers.
Unified Governance	Automation Center	A single dashboard to monitor the health, security, and ROI of all agents and flows across the tenant.

Reference

2025 release wave 2 plans for Microsoft Dynamics 365, Microsoft Power Platform, and Role-based Microsoft Copilot offerings

Uncategorized

Use least active routing on messaging channels in Dynamics 365 Contact Centre

July 13, 2025May 3, 2026 Goloknath

Use least active routing on messaging channels

(Extending intelligent workload distribution from voice to digital messaging channels to ensure fair agent utilization).

Real-time User Journey

This journey illustrates how the system balances work across a blended workforce (agents handling both voice and chat):

Scenario Setup: Two agents, Oscar and Victoria, have identical skills. Oscar is currently handling 1 chat. Victoria is handling 1 voice call and 1 chat.
New Incoming Request: A new customer starts a chat on the website.
Concurrency Check: The routing engine evaluates current workloads. It identifies that Oscar has fewer concurrent assignments (1) than Victoria (2).
Initial Assignment: The chat is assigned to Oscar to balance the total number of active conversations.
Tie-Breaking (Last Capacity Release): Later, two different agents, Maya and Hailey, both have exactly 1 active assignment.
Time-based Decision: The engine checks their “Last Capacity Release Time” (when they finished their previous task). Maya finished her last chat at 1:55 PM, while Hailey finished at 2:00 PM.
Final Routing: Because Maya has been “inactive” longer, the new chat is routed to her, ensuring Hailey gets a fair amount of “rest” time between tasks.

Step-by-Step: How to Enable This Feature

To implement least active routing in your messaging queues:

Step 1: Admin Center Access

Step 2: Select the Queue

Navigate to Customer Support > Queues. Open the specific messaging queue (e.g., Chat, WhatsApp, or SMS) where you want to apply this logic.

Step 3: Set Assignment Method

In the Assignment method section, select Least active from the dropdown menu.

Step 4: Configure Custom Assignment (Optional)

If you use “Custom” assignment methods, you can add “Least active” as an Order by condition. This allows you to first filter by “Highest Skill” and then use “Least Active” as the tie-breaker.

Step 5: Verify Capacity Profiles

Ensure that your agents have Capacity Profiles defined (e.g., an agent can handle 100 points of work, where a chat is 20 points). Least active routing relies on these profiles to calculate concurrent load.

Step 6: Data Tracking (Advanced)

To build reports on this, use the Dataverse entity msdyn_agentchannelstateentity. This tracks the lastcapacityreleasetime for each agent, which powers the routing decisions.

Infographic: How Least Active Routing Works

Factor	Description	Benefit
Concurrent Load	Counts the number of active calls and chats currently assigned.	Prevents overloading individual agents.
Last Capacity Release	Tracks the exact timestamp when the last conversation ended.	Ensures fair “breathing room” between tasks.
Cross-Channel Aware	Considers both Voice and Messaging work items together.	Perfectly balances a “Blended” workforce.
Fair Utilization	Moves agents toward a consistent utilization percentage (e.g., 85%).	Reduces burnout and improves agent satisfaction.
SLA Stability	Prioritizes available capacity over random assignment.	Keeps wait times consistent for customers.

References

Use least active routing on messaging channels

Uncategorized

Synchronize service rep availability across platforms with Presence APIs in Dynamics 365

July 12, 2025May 3, 2026 Goloknath

Synchronize service rep availability across platforms with Presence APIs

(Achieving a “Single Source of Truth” for agent availability across Dynamics 365, Microsoft Teams, and third-party applications).

Real-time User Journey

This journey illustrates how the Presence APIs eliminate the “Double Work” of managing status across multiple communication tools:

Unified Login: A service representative logs into the Dynamics 365 Contact Center.
Automatic Sync: The Presence API immediately detects the agent’s “Available” status in Dynamics 365 and automatically updates their Microsoft Teams status to “Available.”
External Trigger: The agent receives an urgent call on a third-party legacy desk phone system integrated via the API.
Real-time State Change: The Presence API detects the “Busy” state on the external phone and instantly switches the agent to “Busy – On a Call” in both Dynamics 365 and Teams.
Routing Protection: Because the status is synchronized, the Unified Routing engine sees the “Busy” state and stops routing new chats or cases to the agent, preventing them from being overwhelmed.
Shift Completion: When the agent’s shift ends in the Workforce Management module, the API pushes an “Offline” status to all connected platforms simultaneously.

Step-by-Step: How to Enable This Feature

The Presence APIs are part of the Microsoft Graph and Dynamics 365 developer toolkit. To enable synchronization, follow these steps:

Step 1: Admin Center Configuration

Step 2: Enable Teams Presence Sync

Locate the setting for “Microsoft Teams presence synchronization” and toggle it to On. This enables the native link between the two Microsoft platforms.

Step 3: Register Application for External Sync

To sync with 3rd party apps, go to the Azure Portal > App Registrations. Register your external application and grant it Presence.Read.All and Presence.ReadWrite.All permissions.

Step 4: Configure API Endpoints

In your external application code, call the Dynamics 365 Presence APIs (GET and SET presence) to pull or push status updates.

Step 5: Define Presence Mapping

In Dynamics 365, go to Presence States and ensure your custom statuses (e.g., “In a Meeting”) are mapped to the correct base statuses (e.g., “Busy”) so the API knows how to translate them across platforms.

Step 6: Test Synchronization

Change your status in Microsoft Teams and verify that the change reflects in the Dynamics 365 agent dashboard within seconds.

Infographic: The Unified Presence Ecosystem

Capability	Without Presence APIs	With Presence APIs
Status Management	Manual update in every app.	Automatic Sync: Update once, reflect everywhere.
Routing Accuracy	High risk of routing to “Busy” agents.	100% Accuracy: Routing respects all active states.
Supervisor View	Conflicting data on agent activity.	Real-time Visibility: One true view of team capacity.
Agent Experience	High cognitive load and “Status Anxiety.”	Seamless Flow: Focus on the customer, not the toggle.
Third-party Apps	Isolated silos of information.	Integrated Ecosystem: Legacy tools stay in sync.

References

Synchronize service rep availability across platforms with presence APIs