Tag: llm

copilot-studio, Power Apps

Inside the New Power Apps: A Reimagined Developer Experience for the Agentic Era

Goloknath

This update introduces a completely new developer surface (located at vibe.powerapps.com) that combines “vibe coding” (high-speed, natural language development) with enterprise-grade scalability. It redefines app development by using a team of specialized AI agents to build full-stack applications.

Real-time User Journey: Multi-Agent App Creation

The new user journey shifts from “dragging and dropping” to “collaborative directing”:

  1. Vision Prompting: A maker describes a complex business problem in natural language: “I need an app for our field technicians to track equipment repairs, check inventory parts in real-time, and automatically notify customers via email.”
  2. Agent Collaboration: A team of agents springs into action:
    • The Researcher Agent: Outlines detailed user stories and functional requirements.
    • The Data Agent: Proposes and builds an optimized data model in Dataverse.
    • The UI/UX Agent: Drafts the modern, responsive interface including forms and galleries.
  3. Real-time Preview: Within minutes, the maker sees a full-stack, functional “draft” of the app.
  4. Human-in-the-Loop Refinement: The maker can give iterative feedback (e.g., “Make the status buttons color-coded”) and the agents update the code and logic immediately.
  5. Seamless Handoff: Once satisfied, the app is ready for deployment with built-in governance, security, and the Power Apps MCP Server already configured to interact with other agents.

Step-by-Step: How to Enable the New Power Apps

Note: This feature was launched at Ignite 2025 and is being rolled out to Managed Environments.

  • Step 1: Access the New Portal: Navigate to the new developer entry point at vibe.powerapps.com.
  • Step 2: Environment Readiness: Ensure your environment is a Managed Environment in the Power Platform Admin Center to support agentic capabilities.
  • Step 3: Enable Copilot & Agents: Under the environment settings, ensure the Generative AI and Copilot features are toggled to “On.”
  • Step 4: Use the MCP Server: To allow your apps to interact with agents (like M365 Copilot), enable the Power Apps Model Context Protocol (MCP) Server in the app settings. This allows agents to “read” your app’s screens and perform tasks like intelligent form filling.
  • Step 5: Governance Setup: In the Admin Center, configure the new Inventory and Usage reporting to monitor the agents and apps created in this new environment.

Infographic: Reimagining App Development

This update marks a shift from “Low-Code” to “Agentic-Code”:

PillarLegacy Power AppsThe New Power Apps (2026 Wave)
Development StyleManual drag-and-drop components.Vibe Coding (Natural language + Agents).
BrainpowerSingle maker expertise.Team of Specialized Agents (Data, UI, Research).
ConnectivityManual connector configuration.MCP Server (Apps provide “skills” to agents).
SpeedHours or days to MVP.Minutes from prompt to full-stack app.
GovernanceManual app auditing.AI-Powered Governance with real-time risk assessment.

References

Inside the new Power Apps: The future of app development
Uncategorized

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

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”:

  1. 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.”
  2. Architectural Blueprint: The Power Apps Design Agent instantly drafts the full app structure—proposing a data schema, user roles, and screen layouts.
  3. 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.
  4. 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?”
  5. 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:

FeatureLegacy Power AppsThe New Power Apps
Creation MethodManual UI & logic building.Generative Plans & Vibe-Coding.
User ExperienceStatic forms and galleries.Agent Feed (Interactive AI assistance).
Data InteractionManual Filter/Search queries.Natural Language Reasoning over data.
Developer ToolsExpression language (Power Fx).Multi-Agent Collaboration (AI handles the Fx).
GovernanceReactive (post-build audits).Proactive (AI-guided security guardrails).

References

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

What’s New in Copilot Studio: April 2025 – Advancing Multi-Agent Orchestration and Connected Experiences

Goloknath

The April 2025 update focused on the release of the Multi-Agent Orchestration engine and the introduction of Agent-to-Agent (A2A) connectivity, allowing agents to work together as a unified system.

Real-time User Journey: Collaborative Multi-Agent Resolution

The core journey introduced this month involves “handoffs” between specialized agents to solve a complex user request:

  1. Request: A user asks a general “HR Agent” in Teams, “I’m traveling to London for a client meeting next week; can you handle my travel booking and ensure it complies with our latest policy?”
  2. Orchestration: The HR Agent realizes it doesn’t have booking permissions. Using the new Orchestration Engine, it identifies a specialized “Travel Booking Agent” and a “Policy Compliance Agent.”
  3. Collaborative Execution: * The Policy Agent retrieves the travel policy from SharePoint and provides the budget limits to the Travel Agent.
    • The Travel Agent searches for flights and hotels that fit those limits.
  4. Verification: The agents pass data back and forth to confirm the hotel choice is within the allowed budget.
  5. Completion: The primary HR Agent returns to the user with a single message: “I’ve found a flight and hotel that comply with our policy. Would you like me to book them?”

Step-by-Step: How to Enable Multi-Agent Connectivity

To allow your agents to communicate with one another using the new protocol:

  • Step 1: Open Copilot Studio: Navigate to your primary agent.
  • Step 2: Enable Orchestration: Go to Settings > Generative AI and toggle the orchestration mode to “Generative (Preview)” or “Multi-agent.”
  • Step 3: Register Sub-Agents: Go to the Actions or Tools tab and select “Add an Agent.” You can now select other agents published within your environment.
  • Step 4: Define Descriptions: Ensure each sub-agent has a highly detailed Instructional Description. The orchestrator uses these to “know” which agent is the expert in travel, finance, or technical support.
  • Step 5: Configure Permissions: Set up Delegated Authentication so the sub-agents can act on behalf of the user who started the original chat.
  • Step 6: Test & Publish: Use the “Test” pane to watch the “Conversation Map” and see how the orchestrator routes the logic between agents.

Infographic: The April 2025 Feature Set

The April update brought several tools to manage complex AI ecosystems:

FeatureWhat it DoesImpact on Business
Multi-Agent OrchestrationAllows a “Master Agent” to manage “Sub-Agents.”Reduces the need for users to know which specific bot to talk to.
A2A Protocol SupportOpen standard for agent-to-agent communication.Enables agents to talk across different platforms (e.g., Copilot to custom Azure bots).
Conversation MapsVisual debugging tool for orchestration.Helps developers see exactly where a handoff happened or failed.
Knowledge HandoffContext is passed between agents during a handoff.The user doesn’t have to repeat their information to the second agent.

References

What’s new in Copilot Studio: April 2025