Phoebe Makes Cloud Simple

I built a Local RAG App — and documented the whole journey on YouTube!

From vector search to a full UI, the series covers everything:

• LangChain
• ChromaDB
• Streamlit
• FastAPI
• Custom Connectors
• Microsoft Graph Integration
No cloud dependency. No data leaving your machine. Just a fully local, production-ready RAG system built step by step.

👉 Watch the full playlist: www.youtube.com/playlist?list...

Would love your feedback — and subscribe for more! 🙌

#RAG #LangChain #ChromaDB #FastAPI #Streamlit #MicrosoftGraph #AI #MachineLearning #LocalAI #Python #GenerativeAI #AIEngineering

2 days ago | [YT] | 1

Phoebe Makes Cloud Simple

I put together a full Copilot Cowork playlist covering the journey from licensing and admin setup to real demos. 🎥



If you’re trying to understand:
✅ What license you need
✅ How to enable and set up Copilot Cowork
✅ What it can actually do in Microsoft 365
✅ How it helps with meetings, tasks, emails, documents, and follow-ups



You can watch the full playlist here:
www.youtube.com/playlist?list...




More demos coming soon as I continue testing what Cowork can do in real work scenarios.

#Microsoft365Copilot #CopilotCowork #Copilot #AIProductivity #PowerPlatform

1 month ago | [YT] | 1

Phoebe Makes Cloud Simple

🚀 New series alert! I'm building a Copilot Studio Scheduling Agent — the right way.

Part 1 is live: the architecture that keeps AI agents reliable 👇


• Parent Agent → routes only
• Instruction Skills → the procedures
• Flow Tools → Power Automate does the actions
• Backed by Dataverse + SharePoint



Key rule: the agent knows the tool contract, not the database schema.

5 parts. Real build. No fluff. Follow along 🎬

https://youtu.be/5d_8W_PXrvQ



🌐 d365phoebe.com

#CopilotStudio #AIAgent #PowerPlatform #PowerAutomate #Dataverse #Microsoft365

1 month ago | [YT] | 0

Phoebe Makes Cloud Simple

𝗗𝗶𝗱 𝘆𝗼𝘂 𝗸𝗻𝗼𝘄? One PAC CLI command replaces an entire 7-step manual process when creating a Power Platform service principal. 🤯

Here's both methods, end to end — so you can pick the right one for your scenario.

🟢 𝗠𝗘𝗧𝗛𝗢𝗗 𝟭 — 𝗧𝗵𝗲 𝗣𝗔𝗖 𝗖𝗟𝗜 𝘄𝗮𝘆 (𝟭 𝗰𝗼𝗺𝗺𝗮𝗻𝗱)
𝚙𝚊𝚌 𝚊𝚍𝚖𝚒𝚗 𝚌𝚛𝚎𝚊𝚝𝚎-𝚜𝚎𝚛𝚟𝚒𝚌𝚎-𝚙𝚛𝚒𝚗𝚌𝚒𝚙𝚊𝚕 --𝚎𝚗𝚟𝚒𝚛𝚘𝚗𝚖𝚎𝚗𝚝 <𝚎𝚗𝚟𝚒𝚛𝚘𝚗𝚖𝚎𝚗𝚝-𝚒𝚍> --𝚛𝚘𝚕𝚎 "𝚂𝚢𝚜𝚝𝚎𝚖 𝙰𝚍𝚖𝚒𝚗𝚒𝚜𝚝𝚛𝚊𝚝𝚘𝚛"
𝗢𝗽𝘁𝗶𝗼𝗻𝗮𝗹 𝗽𝗮𝗿𝗮𝗺𝗲𝘁𝗲𝗿𝘀: • --𝚗𝚊𝚖𝚎 — display name for the app • --𝚛𝚘𝚕𝚎 — security role (default: System Administrator) • --𝚎𝚗𝚟𝚒𝚛𝚘𝚗𝚖𝚎𝚗𝚝 — target environment ID

𝗪𝗵𝗮𝘁 𝘁𝗵𝗶𝘀 𝘀𝗶𝗻𝗴𝗹𝗲 𝗰𝗼𝗺𝗺𝗮𝗻𝗱 𝗱𝗼𝗲𝘀 𝗳𝗼𝗿 𝘆𝗼𝘂:
1️⃣ Creates a new Entra ID app registration
2️⃣ Creates a service principal for that app
3️⃣ Generates a client secret
4️⃣ Registers the app with Power Platform
5️⃣ Creates an application user in the target environment
6️⃣ Assigns the specified security role

𝗢𝘂𝘁𝗽𝘂𝘁 𝘆𝗼𝘂 𝗴𝗲𝘁 𝗯𝗮𝗰𝗸: • Tenant ID • Application (client) ID • Client secret • Expiration date
Done. Seconds. One terminal window.

🔴 𝗠𝗘𝗧𝗛𝗢𝗗 𝟮 — 𝗧𝗵𝗲 𝗠𝗮𝗻𝘂𝗮𝗹 𝘄𝗮𝘆 (𝟳+ 𝘀𝘁𝗲𝗽𝘀, 𝟯 𝗽𝗼𝗿𝘁𝗮𝗹𝘀)
➡️𝗦𝘁𝗲𝗽 𝟭 — 𝗥𝗲𝗴𝗶𝘀𝘁𝗲𝗿 𝗮𝗻 𝗮𝗽𝗽 𝗶𝗻 𝗘𝗻𝘁𝗿𝗮 𝗜𝗗 Azure Portal → Microsoft Entra ID → App registrations → New registration • Set a name • Choose "Single tenant" (or multi-tenant if needed) • Click Register • Save the 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 (𝗰𝗹𝗶𝗲𝗻𝘁) 𝗜𝗗 and 𝗗𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆 (𝘁𝗲𝗻𝗮𝗻𝘁) 𝗜𝗗

➡️𝗦𝘁𝗲𝗽 𝟮 — 𝗖𝗿𝗲𝗮𝘁𝗲 𝗮 𝗰𝗹𝗶𝗲𝗻𝘁 𝘀𝗲𝗰𝗿𝗲𝘁 Inside the app → Certificates & secrets → New client secret • Set description and expiration • 𝗖𝗼𝗽𝘆 𝘁𝗵𝗲 𝘀𝗲𝗰𝗿𝗲𝘁 𝘃𝗮𝗹𝘂𝗲 𝗶𝗺𝗺𝗲𝗱𝗶𝗮𝘁𝗲𝗹𝘆 (you won't see it again)

➡️𝗦𝘁𝗲𝗽 𝟯 — 𝗔𝗱𝗱 𝗔𝗣𝗜 𝗽𝗲𝗿𝗺𝗶𝘀𝘀𝗶𝗼𝗻𝘀 (𝗼𝗽𝘁𝗶𝗼𝗻𝗮𝗹, 𝘀𝗰𝗲𝗻𝗮𝗿𝗶𝗼-𝗱𝗲𝗽𝗲𝗻𝗱𝗲𝗻𝘁) API permissions → Add a permission → Dynamics CRM → user_impersonation → Grant admin consent

➡️𝗦𝘁𝗲𝗽 𝟰 — 𝗜𝗻𝘀𝘁𝗮𝗹𝗹 𝘁𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗔𝗽𝗽𝘀 𝗔𝗱𝗺𝗶𝗻 𝗣𝗼𝘄𝗲𝗿𝗦𝗵𝗲𝗹𝗹 𝗺𝗼𝗱𝘂𝗹𝗲
𝗽𝗼𝘄𝗲𝗿𝘀𝗵𝗲𝗹𝗹
𝙸𝚗𝚜𝚝𝚊𝚕𝚕-𝙼𝚘𝚍𝚞𝚕𝚎 -𝙽𝚊𝚖𝚎 𝙼𝚒𝚌𝚛𝚘𝚜𝚘𝚏𝚝.𝙿𝚘𝚠𝚎𝚛𝙰𝚙𝚙𝚜.𝙰𝚍𝚖𝚒𝚗𝚒𝚜𝚝𝚛𝚊𝚝𝚒𝚘𝚗.𝙿𝚘𝚠𝚎𝚛𝚂𝚑𝚎𝚕𝚕 -𝙵𝚘𝚛𝚌𝚎 𝙸𝚗𝚜𝚝𝚊𝚕𝚕-𝙼𝚘𝚍𝚞𝚕𝚎 -𝙽𝚊𝚖𝚎 𝙼𝚒𝚌𝚛𝚘𝚜𝚘𝚏𝚝.𝙿𝚘𝚠𝚎𝚛𝙰𝚙𝚙𝚜.𝙿𝚘𝚠𝚎𝚛𝚂𝚑𝚎𝚕𝚕 -𝙰𝚕𝚕𝚘𝚠𝙲𝚕𝚘𝚋𝚋𝚎𝚛 -𝙵𝚘𝚛𝚌𝚎

➡️𝗦𝘁𝗲𝗽 𝟱 — 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗲 𝘁𝗼 𝗣𝗼𝘄𝗲𝗿 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺
𝗽𝗼𝘄𝗲𝗿𝘀𝗵𝗲𝗹𝗹
𝙰𝚍𝚍-𝙿𝚘𝚠𝚎𝚛𝙰𝚙𝚙𝚜𝙰𝚌𝚌𝚘𝚞𝚗𝚝

➡️𝗦𝘁𝗲𝗽 𝟲 — 𝗥𝗲𝗴𝗶𝘀𝘁𝗲𝗿 𝘁𝗵𝗲 𝗮𝗽𝗽 𝘄𝗶𝘁𝗵 𝗣𝗼𝘄𝗲𝗿 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺
𝗽𝗼𝘄𝗲𝗿𝘀𝗵𝗲𝗹𝗹
𝙽𝚎𝚠-𝙿𝚘𝚠𝚎𝚛𝙰𝚙𝚙𝙼𝚊𝚗𝚊𝚐𝚎𝚖𝚎𝚗𝚝𝙰𝚙𝚙 -𝙰𝚙𝚙𝚕𝚒𝚌𝚊𝚝𝚒𝚘𝚗𝙸𝚍 <𝚊𝚙𝚙𝚕𝚒𝚌𝚊𝚝𝚒𝚘𝚗-𝚒𝚍>
This tells Power Platform to 𝘁𝗿𝘂𝘀𝘁 your Entra ID app as a management app.

➡️𝗦𝘁𝗲𝗽 𝟳 — 𝗖𝗿𝗲𝗮𝘁𝗲 𝘁𝗵𝗲 𝗮𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝘂𝘀𝗲𝗿 𝗺𝗮𝗻𝘂𝗮𝗹𝗹𝘆 Power Platform Admin Center → Environments → [Your environment] → Settings → Users + permissions → Application users → New app user • Add the app (search by Application ID) • Assign business unit • Assign security role (e.g., System Administrator) • Click Create

Skip the Carousel

1 2 3 4 5 6 7 8 9

2 months ago | [YT] | 2

Phoebe Makes Cloud Simple

Building Dataverse Business Skills? Here's the pain nobody warns you about:

Every skill needs files attached. And Power Apps wants you to upload them ONE. AT. A. TIME.

10 skills × 5 files = 50 manual uploads. No thanks.



So I automated it. 👇

The setup (3 pieces):

• Files live on SharePoint • A CSV manifest maps each file to its skill • A Power Automate flow does the rest



The flow:

• Get the CSV from SharePoint • Parse it, split into lines • Loop through each row: • Lookup the parent skill in Dataverse • Pull the file from SharePoint • Create the skillresource row • Upload the file to the environment

One run. Every skill gets its files. Done.



Why it matters:

• An afternoon of clicking → under 2 minutes • Zero misclicks, zero wrong attachments • New skill? Add a row to the CSV, re-run

The Power Apps UI is great for one skill. It's not great for fifty.

Anytime you click the same sequence more than 5 times — that's a flow waiting to be built.



Save this for the next time you're staring down 50 file uploads.

If this helped → 👍 Like, 💬 Comment, 🔁 Repost so the next maker doesn't have to learn it the hard way. 🤍

#CopilotStudio #PowerPlatform #Dataverse #PowerAutomate #SharePoint

2 months ago | [YT] | 1

Phoebe Makes Cloud Simple

There's one thing I wish someone had told me on day one about skills:

There are TWO different types of skills in Copilot Studio. Most people open the wrong one and get stuck.
Let me save you the headache. 👇

When people say "Skills" in Copilot Studio, they could mean one of two completely different things:
• Pro-code Skills • Dataverse Business Skills
Same name. Totally different worlds. Pick the wrong door and nothing works the way you expect.

➡️𝗗𝗼𝗼𝗿 #𝟭 — 𝗣𝗿𝗼-𝗰𝗼𝗱𝗲 𝗦𝗸𝗶𝗹𝗹𝘀
Where you find it: ⚙ Settings › Skills
This door is built for developers. If you have a Bot Framework bot or a custom-coded service sitting somewhere, this is how you plug it in.
• Needs a manifest URL • Code lives in .NET, JavaScript, or Python • Powered by the Microsoft 365 Agents SDK
Quick test: if Copilot Studio is asking you for a manifest URL, you're standing in front of this door.

➡️𝗗𝗼𝗼𝗿 #𝟮 — 𝗗𝗮𝘁𝗮𝘃𝗲𝗿𝘀𝗲 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗦𝗸𝗶𝗹𝗹𝘀
Where you find it: 🛠 Tools › Dataverse MCP
This is the door most makers and business users actually want — and the one that gets missed all the time.
• Zero code • No manifest • No hosting to worry about
Everything is written in plain markdown, right inside Power Apps.

𝗛𝗼𝘄 𝘁𝗼 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝘂𝘀𝗲 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗦𝗸𝗶𝗹𝗹𝘀 (𝟯 𝗺𝗼𝘃𝗲𝘀):
1️⃣ Build it in Power Apps → open your Dataverse environment, create the skill, describe what it does in markdown, you can add files too and save.
2️⃣ Wire it up in Copilot Studio → go to Tools, add the Dataverse MCP Server connection, sign in to the same environment.
3️⃣ Talk to your agent → open the test pane and try: "Show me all business skills in this environment" "Run Customer Onboarding"
That's it. Your agent finds them and runs them through MCP.

𝗦𝗼 𝘄𝗵𝗶𝗰𝗵 𝗱𝗼𝗼𝗿 𝗶𝘀 𝘆𝗼𝘂𝗿𝘀?
• Existing Bot Framework bot to integrate? → Pro-code
• Want makers and business users to extend your agent in plain language? → Business Skills

🔁 The flow that actually works:
Build in Power Apps → Connect Dataverse MCP → Test in Copilot Studio
Here's what nobody tells you…
"Skills" in Copilot Studio isn't one feature. It's two different products that happen to share a name. Once that clicked for me, everything got easier.
I stopped wrestling with manifest URLs. I stopped Googling the same Stack Overflow threads. I am starting to ship agents the way they were actually designed to be built.
If this cleared something up for you, save the post , you'll come back to it.
And Like, comment and share.
#CopilotStudio #PowerPlatform #Dataverse #MCP #PowerApps #LowCode #AIAgents

Skip the Carousel

1 2 3 4 5 6 7 8 9

2 months ago | [YT] | 1

Phoebe Makes Cloud Simple

𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝗣𝗼𝘄𝗲𝗿 𝗔𝗽𝗽𝘀 𝗖𝗼𝗱𝗲𝗔𝗽𝗽𝘀 - 𝗠𝘆 𝗖𝗼𝗺𝗺𝗮𝗻𝗱 𝗖𝗵𝗲𝗮𝘁 𝗦𝗵𝗲𝗲𝘁

1️⃣𝗜𝗻𝗶𝘁𝗶𝗮𝗹 𝗦𝗲𝘁𝘂𝗽:
𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 𝚗𝚙𝚖 𝚛𝚞𝚗 𝚍𝚎𝚟 𝚙𝚊𝚌 𝚌𝚘𝚍𝚎 𝚒𝚗𝚒𝚝 --𝚍𝚒𝚜𝚙𝚕𝚊𝚢𝙽𝚊𝚖𝚎 "𝙿𝚘𝚠𝚎𝚛 𝙰𝚞𝚝𝚘𝚖𝚊𝚝𝚎 𝙸𝚗𝚝𝚎𝚐𝚛𝚊𝚝𝚒𝚘𝚗 𝙲𝚘𝚍𝚎𝙰𝚙𝚙" -𝚎𝚗𝚟 <𝚎𝚗𝚟𝚒𝚍>
C͟r͟e͟a͟t͟e͟s͟ ͟p͟o͟w͟e͟r͟.͟c͟o͟n͟f͟i͟g͟.͟j͟s͟o͟n͟

2️⃣𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻:
𝚙𝚊𝚌 𝚘𝚛𝚐 𝚕𝚒𝚜𝚝 𝚙𝚊𝚌 𝚘𝚛𝚐 𝚜𝚎𝚕𝚎𝚌𝚝 --𝚎𝚗𝚟𝚒𝚛𝚘𝚗𝚖𝚎𝚗𝚝 <𝚎𝚗𝚟𝚒𝚍> 𝚙𝚊𝚌 𝚊𝚞𝚝𝚑 𝚌𝚕𝚎𝚊𝚛 𝚙𝚊𝚌 𝚊𝚞𝚝𝚑 𝚕𝚒𝚜𝚝 𝚙𝚊𝚌 𝚊𝚞𝚝𝚑 𝚌𝚛𝚎𝚊𝚝𝚎 -𝚞𝚛𝚕 <𝚎𝚗𝚟𝚞𝚛𝚕>

3️⃣𝗔𝗱𝗱 𝗗𝗮𝘁𝗮 𝗦𝗼𝘂𝗿𝗰𝗲𝘀:

𝗗𝗮𝘁𝗮𝘃𝗲𝗿𝘀𝗲:
𝚙𝚊𝚌 𝚌𝚘𝚍𝚎 𝚊𝚍𝚍-𝚍𝚊𝚝𝚊-𝚜𝚘𝚞𝚛𝚌𝚎 -𝚊 𝚍𝚊𝚝𝚊𝚟𝚎𝚛𝚜𝚎 -𝚝 <𝚝𝚊𝚋𝚕𝚎𝚗𝚊𝚖𝚎>
𝗦𝗵𝗮𝗿𝗲𝗣𝗼𝗶𝗻𝘁:
𝚙𝚊𝚌 𝚌𝚘𝚍𝚎 𝚊𝚍𝚍-𝚍𝚊𝚝𝚊-𝚜𝚘𝚞𝚛𝚌𝚎
-𝚊 "𝚜𝚑𝚊𝚛𝚎𝚍_𝚜𝚑𝚊𝚛𝚎𝚙𝚘𝚒𝚗𝚝𝚘𝚗𝚕𝚒𝚗𝚎"
-𝚌 "<𝚌𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗-𝚒𝚍>"
-𝚝 "𝚁𝚎𝚊𝚜𝚘𝚗 𝙲𝚘𝚍𝚎𝚜"
-𝚍 "𝚑𝚝𝚝𝚙𝚜://𝚑𝚘𝚜𝚝𝚗𝚊𝚖𝚎.𝚜𝚑𝚊𝚛𝚎𝚙𝚘𝚒𝚗𝚝.𝚌𝚘𝚖/𝚜𝚒𝚝𝚎𝚜/𝚜𝚒𝚝𝚎𝚗𝚊𝚖𝚎"

4️⃣𝗚𝗲𝘁 𝗖𝗼𝗻𝗻𝗲𝗰𝘁𝗶𝗼𝗻𝘀:
𝚙𝚊𝚌 𝚌𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗 𝚕𝚒𝚜𝚝 > 𝚌𝚘𝚗𝚗𝚎𝚌𝚝𝚒𝚘𝚗𝚜.𝚝𝚡𝚝

5️⃣𝗕𝘂𝗶𝗹𝗱 & 𝗗𝗲𝗽𝗹𝗼𝘆:
𝚗𝚙𝚖 𝚛𝚞𝚗 𝚋𝚞𝚒𝚕𝚍 𝚙𝚊𝚌 𝚌𝚘𝚍𝚎 𝚙𝚞𝚜𝚑 𝚗𝚙𝚡 𝚙𝚘𝚠𝚎𝚛-𝚊𝚙𝚙𝚜 𝚛𝚞𝚗

⚙️ 𝗔𝗱𝘃𝗮𝗻𝗰𝗲𝗱:
6️⃣𝗔𝗱𝗱 𝗖𝘂𝘀𝘁𝗼𝗺 𝗔𝗰𝘁𝗶𝗼𝗻𝘀:
𝚗𝚙𝚡 𝚙𝚘𝚠𝚎𝚛-𝚊𝚙𝚙𝚜 𝚊𝚍𝚍-𝚍𝚊𝚝𝚊𝚟𝚎𝚛𝚜𝚎-𝚊𝚙𝚒 -𝚗 𝚙𝚗_𝙶𝚎𝚝𝚁𝚎𝚚𝚞𝚎𝚜𝚝𝙸𝚝𝚎𝚖𝚜
𝚗𝚙𝚡 𝚙𝚘𝚠𝚎𝚛-𝚊𝚙𝚙𝚜 𝚏𝚒𝚗𝚍-𝚍𝚊𝚝𝚊𝚟𝚎𝚛𝚜𝚎-𝚊𝚙𝚒 --𝚜𝚎𝚊𝚛𝚌𝚑 "𝚙𝚗_𝙶𝚎𝚝𝚁𝚎𝚚𝚞𝚎𝚜𝚝𝙸𝚝𝚎𝚖𝚜"
7️⃣𝗖𝗵𝗲𝗰𝗸 𝗩𝗲𝗿𝘀𝗶𝗼𝗻:
𝚗𝚙𝚖 𝚒𝚗𝚜𝚝𝚊𝚕𝚕 @𝚖𝚒𝚌𝚛𝚘𝚜𝚘𝚏𝚝/𝚙𝚘𝚠𝚎𝚛-𝚊𝚙𝚙𝚜@𝚕𝚊𝚝𝚎𝚜𝚝 𝚗𝚙𝚖 𝚕𝚜 @𝚖𝚒𝚌𝚛𝚘𝚜𝚘𝚏𝚝/𝚙𝚘𝚠𝚎𝚛-𝚊𝚙𝚙𝚜 # 𝚂𝚑𝚘𝚞𝚕𝚍 𝚋𝚎 𝟷.𝟷.𝟷+

💡 𝗣𝗿𝗼 𝗧𝗶𝗽: Save these commands. You'll use them every single project.
#PowerApps #CodeApps #PowerPlatform #ProDev #CLI
👉 𝗪𝗵𝗮𝘁'𝘀 𝘆𝗼𝘂𝗿 𝗴𝗼-𝘁𝗼 𝗣𝗼𝘄𝗲𝗿 𝗣𝗹𝗮𝘁𝗳𝗼𝗿𝗺 𝗖𝗟𝗜 𝗰𝗼𝗺𝗺𝗮𝗻𝗱?

Skip the Carousel

1 2 3 4 5 6 7 8 9 10

2 months ago | [YT] | 2

Phoebe Makes Cloud Simple

The RIGHT Way to Wire Power Automate into Power Apps Code App

What I Was Doing Wrong:
HTTP fetch with manual auth tokens
Fighting CORS issues
Maintaining brittle URLs


✅ What I Fixed:
Switched to the new SDK approach
Cleaner, faster, more reliable
📋 3 Simple Steps:
Step 1: Use PowerApps (V2) trigger
Define clear input/output contracts
Step 2: Run one command:

npx power-apps add-flow --flow-id <id>
✅ Generates bindings
✅ Registers flow
✅ Wires authentication automatically

Step 3: Make typed calls in CustomPage.tsx
🔒 Auth handled for you
💡 Full IntelliSense support

🟢 Why This Matters:
No CORS headaches
Auth via session (automatic)
TypeScript safety (fewer bugs)
ALM-ready (proper deployment)
Tracked in power.config.json

The Bottom Line:
One command. Everything just works.

npx power-apps add-flow --flow-id <your-flow-id>
lnkd.in/eFWTp5ZT

#PowerApps #PowerAutomate #LowCode #TypeScript #ProDev

2 months ago | [YT] | 2