Seth_Patton For the App Builder agent, do you have more details on this? Our understanding is that it creates a new SharePoint site for every single app and provisions a List within that SharePoint site that's used by the app.
- Any plans for us to use an existing SharePoint site, or multiple lists within a single SharePoint site?
- What type of site is provisioned (group vs. non-group connected, site template, etc.)?
- When the app is deleted, it's supposed to also delete the associated SharePoint site - but what happens if someone has added additional content, lists/libraries, etc. in that SharePoint site - will that also be completely deleted when the app is deleted?
Also, the REACT app is built (stored) within a dedicated Power Platform environment and not accessible even by Admins to see the REACT code. Given REACT apps generally install third-party/community packages, and those have dependencies installed, how do we know that it's not using a package that hasn't been updated for 3+ years and has possible exploits, other risks, etc. that could potentially affect our tenant? This is quite common when working with Copilot for GitHub where it tries to add packages that are extremely old and not supported, etc. but we have control in that instance since we are working directly with the code. Given our admins can't even get access to the REACT code, we have no idea what's happening behind the scenes.