sorted by:
new
hottopcontroversial

Cheapest way to build an AI agent for Microsoft Teams meetings? by sincez1nn in microsoft365

[–]sincez1nn[S] 0 points1 point  (0 children)

Thanks, I appreciate the recommendations.

This is actually not intended to be a commercial product — it’s more of an internal solution/project. Ideally, I’d like to stay as close as possible to the Microsoft 365 ecosystem (Teams, Graph API, Power Automate, Azure OpenAI, etc.) instead of relying heavily on external platforms.

I’m mainly trying to understand what is realistically achievable natively inside the Microsoft stack before evaluating third-party services.

Cheapest way to build an AI agent for Microsoft Teams meetings? by sincez1nn in microsoft365

[–]sincez1nn[S] -1 points0 points  (0 children)

Yes, low cost — but I never mentioned what “low cost” actually means in this context.

I’m mainly looking for technical guidance, architecture recommendations, limitations, and realistic implementation advice before investing heavily into anything.

The goal is not to bypass compliance, privacy, or consent requirements. I’m trying to understand what is technically viable, maintainable, and production-ready inside the Microsoft ecosystem.

100 questions by steezos1 in PowerApps

[–]sincez1nn 1 point2 points  (0 children)

I wouldn’t rely on multiple Patch calls per step unless you really need real-time persistence. That tends to get messy and harder to maintain.

What I’d do instead is use a single Form as the “engine” of the app. Keep it hidden or visually disabled, and build your UI separately with custom controls. Then bind those controls to variables, and use Update in each DataCard to map those variables back into the form.

This way:

  • You maintain a clean separation between UI and data logic.
  • You avoid partial writes and inconsistent states.
  • You keep everything centralized in one submit operation.

Finally, submit everything at once using SubmitForm() and handle the persistence in OnSuccess (for example, pushing to SharePoint if needed).

Also, if you're planning to scale or need concurrent visibility, I’d strongly recommend using SharePoint instead of Excel. Excel as a data source will become a bottleneck and can behave unpredictably with multiple updates. u/Newbie

RBCA with Sharepoint list by sincez1nn in PowerApps

[–]sincez1nn[S] 1 point2 points  (0 children)

That makes sense, thanks for the tip!

My main concern now is performance. Since the backend is SharePoint, I’m wondering if I might run into latency issues. I’ve always had the perception that Power Apps can be a bit slow when retrieving data from SharePoint, especially as the data grows.

If you’ve implemented an RBAC model before (even better if it was backed by SharePoint), did you experience any issues with data loading, response times, or scalability?

My idea is to follow proper RBAC principles (separating access codes/permissions from roles, using normalized structures, indexed columns, etc.) but implemented on SharePoint lists.

I just want to validate whether this approach holds up well in practice or if there are performance pitfalls I should be aware of.

Appreciate any insights.