Merge branch 'master' of https://github.com/microsoft/powerapps-tools

Administration/CoEStarterKit/README.md

@@ -7,6 +7,7 @@ Please find all information on how to install and use the kit on https://docs.mi
 ### Latest Update
 Date | Notes
 ---|---
+2021.05.06 | Small bug fixes to all components |
 2021.04.08 | **Core Components**: We are now capturing Capacity and Add-On information for Environments. Information is captured in the Admin \| Sync Template v3 flow, and written to new Environment Capacity and Environment Add-On tables that have a 1:n relationship with Environment. We also added an Environment Business Area table that allows a customer to add a cost code, business area, and environment owner to an Environment - an admin would have to manually add this information in the model driven app. Admins can also set approved capacity and receive alerts when environments are over or close to their approved capacity. No enforcement takes place here, of course, it's just a number to compare to. We have added the Admin \| Welcome Email and App Catalog, previously in Nurture, to Core in an effort to uncouple Nurture from Core and allow it to be installed stand-alone. With the current release, there's still a dependency on the CoE settings table in Core but with the next release we will move those settings to Environment Variables. The Power BI Report has been changed from Import to DirectQuery mode and is using the new Dataverse connector to get the data now. This means you will have to have access to the underlying data to view the report and you will no longer need to set a schedule refresh on the dataset. We decomissioned the Audit Log flows that used basic authentication.<br>**Core Components for Teams**: The CoE Starter Kit can now be installed in Dataverse for Teams environments, docs will be updated with setup instructions - for Core, a forked solution called Core for Teams will have to be used. <br>**Governance Components**: This solution can be installed in both Production and Dataverse for Teams environment (the same solution). The Developer Compliance Center has been updated with a new responsive layout and teams look. We have added a new Environment variable to allow customers to exclude the Default environment from the Admin \| Compliance detail request flow, based on customer feedback. <br>**Nurture Components**: This solution can be installed in both Production and Dataverse for Teams environment (the same solution). All apps have been updated with a new responsive layout and teams look. We have developed a new tool called Maker Assessment which has been added to the Nurture solution. This app will take a maker through a set of questions, and they will receive governance and license considerations to keep in mind prior to building the solution. The goal is for a maker to make the best decision possible based on what their internal policies and support is (e.g. they won't start using AI Builder with a trial if their company is not ready to support this yet). We provide a starter set of questions that customers can update and change with an admin app.
 2021.03.03 | **Core Components**: Sync Flow (Apps) has been optimized into seperate loops. PowerApps App and Flow tables have new Environment ID fields, and Sync Flow (Apps) and Sync Flow (Flow) flows store the ID to avoid delegation issues in the DLP Editor. DLP Editor v2 has been updated to avoid delegation. **Governance and Nurture components**: canvas apps have been updated with responsive layouts. **Audit Log components** JSON schema has been updated based on customer issues.
 2021.02.03 | ALM Accelerator for Makers (GitHub): Fixed an issue with provisioning environments that was caused by an update to the Power Platform Admin connector #739. Also, included is an update to the default for the environment variable that dictates the GitHub template to use when provisioning a new GitHub repo #708