Releases: microsoft/coe-starter-kit
CoE Starter Kit November 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/18?closed=1
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Change Log
- #447-[Nurture Components] Training in a day - add calendar item to email
- #1082-[CoE Starter Kit - BUG] can not turn on BPF for approving Teams environments
- #1110-[CoE Starter Kit] Environment Request App - Improve filter on my pending requests view
- #1143-[CoE Starter Kit - Enhancement] Developer Compliance Center - make filter based on Power Platform User Role so you can get editors too
- #1153-Add app ownership change request to Developer Compliance Center
- #1163-[CoE Starter Kit - BUG] In Capacity part of the PowerBI DashBoard I am getting blank Environment Names
- #1238-[CoE Starter Kit] Exclude environment from Compliance flow should also exclude it from Developer Compliance Center
- #1239-[CoE Starter Kit] Developer Compliance Center enhancements
- #1251-[CoE Starter Kit - BUG] Power Platform Resource RMS - haven't shown the icon of connectors are not restricted.
- #1254-[CoE Starter Kit - BUG] Admin | Sync Template v3 (Connectors) taking 3+ days to run
- #1287-[CoE Starter Kit] Re-design Developer Compliance Center app
- #1318-[CoE Starter Kit - BUG] Admin - Environment Request filter works not as expected
- #1319-[CoE Starter Kit - BUG] Inconsistent usage of environment variable in App Catalog
- #1320-[CoE Starter Kit - BUG] DLP Editor v2 layout issue
- #1324-[CoE Starter Kit - BUG] Compliance Detail Request Flow - not returning apps for Default envt
- #1325-[CoE Starter Kit - BUG] Set App Permissions - D4T - cant add users to default envt
- #1326-[CoE Starter Kit - BUG] Set App Permissions -D4T - not reading env vars
- #1329-[CoE Starter Kit - BUG] Unneeded tab on Portal form
- #1332-[CoE Starter Kit - BUG] Model Driven Apps sync flow not writing App Environment ID string
- #1333-CoE Starter Kit] Duplicate app GUIDs across different environments
- #1334-Admin | Sync Template v3 (Portals) errors claiming duplicate records
- #1336-[CoE Starter Kit - BUG] Set App Permissions (Dataverse for teams) User photo error.
- #1337-[CoE Starter Kit - BUG] Set Flow approval Dataverse for teams
- #1345-Model apps having the same ItemInternalID across environments only shows in 1 environment
- #1353-[CoE Starter Kit - BUG] - Admin | Sync Template v3 (PVA) - Very long run times & Bad gateway
- #1355-[CoE Starter Kit - BUG] - HELPER - CloudFlowOperations Gov - Unable to process "get_guid_length"
- #1358-[CoE Starter Kit - BUG] case sensitive - CLEANUP - Admin | Sync Template v3 (Check Deleted)
- #1369-[CoE Starter Kit - BUG] "CLEANUP HELPER - Power Apps User Shared With" flow does not save App info
- #1375-[CoE Starter Kit] Include Power Platform release wave notes in Command Centers
- #1384-[CoE Starter Kit - enhancement] add role setting to CanvasAppOperations helper flows
- #1387-[CoE Starter Kit - BUG] Cannot share Developer Compliance Center
- #1391-[CoE Starter Kit] App Catalog - update with feedback option and other enhancements
- #1406-[CoE Starter kit] Add field for environment purpose to enviornment table
- #1417-[CoE Starter Kit - BUG] CLEANUP - Admin | Sync Template v3 (Connection Status) - fails when you run in to deleted apps and flows
- #1418-[CoE Starter Kit - BUG] Check Deleted - PVA and MDA helpers timing out now for Teams sku
CoE Starter Kit October 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/17
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Change Log
- #714-[CoE Starter Kit - Enhancement] More flexibility for Governance and Nurture flows
- #884-[CoE Starter Kit - BUG] Missing Fields in Power BI Dashboard for Dataverse for Teams
- #1043-[CoE Starter Kit - BUG] DLP Editor V2 - Environment disappears on Remove from Policy
- #1096-[CoE Starter Kit - BUG] Not all portals are recorded into the table by the flow
- #1101-[CoE Starter Kit - BUG] Power Platform Request Center Error
- #1133-[CoE Starter Kit - BUG] Command Center flow wont gather model driven apps if gathering apps fails
- #1135-[CoE Starter Kit - BUG] Dataverse CoE Dashboard 202109 has several errors
- #1146-[CoE Starter Kit - Documentation] - Upgrading Audit Log Solution - [Child] Admin | Sync Logs
- #1171-[CoE starter kit Issue] Governance Setup - Request Orphaned Objects Reassigned (Child) Flow Error
- #1176-[CoE Starter Kit - BUG] Clean up flows not respecting Admin eMail variable.
- #1185-Cleanup Power Apps User Shared with takes 4 days to run
- #1187-[CoE Starter Kit] Explain how the Archive Score is calculated in the dashboard
- #1194-[CoE Starter Kit - BUG] Set App Permissions (and flow) - filter on Environment page doesnt work on load
- #1203-[CoE Starter Kit - BUG] Set App Permissions (and flow) - launch button on orphans page doesnt work
- #1208-[CoE Starter Kit - Enhancement] Teams cleanup language is confusing to some users when warned about deletion. Delete Team??? Delete PP Envt???
- #1209-[CoE Starter Kit - BUG] Admin | Compliance detail request v3 - most conditions have one side missing
- #1212-[CoE Starter Kit - DOCUMENTATION] Env Request - Notify Admin flow needs an env variable set before turning on
- #1216-[CoE Starter Kit - BUG] Core Components - CLEANUP - Admin | Sync Template v3 (Check Deleted)
- #1217-[CoE Starter Kit in Teams] Environment Capacity management capability
- #1218-[CoE Starter Kit - BUG] Deleted Custom Connectors not included in CLEANUP - Admin | Sync Template v3 (Check Deleted)
- #1219-[CoE Starter Kit - BUG] Add Manager and M2 Manager to Maker form in Model Driven App
- #1220-[CoE Starter Kit - BUG] Orphaned Object Reassigment flows - return values coming as string not int
- #1223-[CoE Starter Kit - BUG] Sync flow errors mail coming in malformatted
- #1225-[CoE Starter Kit - BUG] Welcome Mail: Make mail go to admin when isProd = false
- #1230-[CoE Starter Kit - BUG] Sync Flow Errors cloud flow is now sending mails even when no data in table
- #1235-[CoE Starter Kit - BUG] Reset solutions to repair the problems with upgrades
- #1237-[CoE Starter Kit - BUG] 'When a HTTP request is received' connector missing from admin_connector table
- #1240-[CoE Starter Kit - BUG] Add Company to Makers table and flows
- #1241-[CoE Starter Kit - BUG] Add Company and Department to Power Platform Users table
- #1249-[CoE Starter Kit - BUG] DLP Editor V2 didn't show the list of Analyzed apps and flows
- #1250-[CoE Starter Kit - REQUEST] Add 'When a HTTP request is received' to the DLP Impact Analysis
- #1252-[CoE Starter Kit - BUG] Improve DLP Editor V2 'Exclude certain environments' experience
- #1255-[CoE Starter Kit - BUG] App Assessment - the line connection between step are not connected.
- #1256-[CoE Starter Kit] Review flows to ensure derived owner trumps owner
- #1263-[CoE Starter Kit - BUG] Active Flows marked as deleted after running CLEANUP HELPER - Check Deleted (Cloud Flows)
- #1278-[CoE Starter Kit - BUG] - Set Flow Permissions - Owner Assignment Error
- #1279-CoE Starter Kit: October
- #1280-[CoE Starter Kit - BUG] PowerBI/Cloud Flows - Table Visualization Filters Broken
- #1288-[CoE Starter Kit] Audit Log flow does not update last launch date
- #1290-[CoE Starter Kit - BUG] COE Filter Issue on New Dashboard
ALM Accelerator For Advanced Makers September 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/13?closed=1
Setup Note
HTTP with Azure AD Connector Configuration
The latest release includes usage of the HTTP with Azure AD Connector. When running the app for the first time you will be prompted to create a new HTTP with Azure AD Connector. Enter the following when prompted (https://graph.microsoft.com).
Create a Service Connection for AA4AM Installation Environment
Additionally, there is a post setup step required to create a Power Platform Service Connection in your Azure DevOps project that points to the environment where AA4AM is installed. In order to create the Service Connection
- Ensure that an Application User is created in your installation environment for AA4AM (see https://github.com/microsoft/coe-starter-kit/blob/main/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md#create-an-app-user-in-your-dataverse-environments for instructions).
- Create a new Service Connection that points to the installation environment for AA4AM (see https://github.com/microsoft/coe-starter-kit/blob/main/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md#create-service-connections-for-devops-to-access-power-platform for instructions).
First Time Setup Instructions
To get started with the ALM Accelerator For Advanced Makers you can
- Use the preview CoE CLI to automate the install at https://github.com/microsoft/coe-starter-kit/blob/main/coe-cli/docs/aa4am/readme.md or in the Power Platform CoE CLI E-Book (Recommended)
- Use the manual setup documentation can be found at https://github.com/microsoft/coe-starter-kit/blob/main/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md
Upgrade Instructions
If you are upgrading to the latest release you will need to perform the following steps.
-
Import the latest AA4AM Solution https://github.com/microsoft/coe-starter-kit/releases/download/ALMAcceleratorForAdvancedMakers-September2021a/ALMAcceleratorForAdvancedMakers_1.0.20211001.1_managed.zip
-
Update your pipeline templates repo with the latest from https://github.com/microsoft/coe-alm-accelerator-templates/archive/refs/tags/ALMAcceleratorForAdvancedMakers-September2021.zip
-
We've removed the dependency on the Power DevOps Tools extension in this release. Any extension that has been removed from this list can be safely removed Install Azure DevOps Extensions.
-
Ensure that you have the latest version of Power Platform Build Tools (1.0.35) installed.
-
Update the Azure DevOps Build Service Permissions to allow the pipelines to configure other pipelines (e.g. setting variables for deployment configuration). Follow the SETUPGUIDE.md to set the permissions.
-
In this release we have updated the pipelines to use deployment configuration files stored in source control rather than using Pipeline variables for the json configuration of Connection References, Environment Variables, Component Ownership, App Sharing etc. We've also split the configuration between a customDeploymentSettings.json and deploymentSettings.json in order to use the built in import task to set environment variables and connection references. Please see DEPLOYMENTCONFIGGUIDE.md for more details.
[!NOTE] If you have previously configured your pipelines using pipeline variables your pipeline variables will no longer work. However, with the addition of functionality to auto generate the deployment configuration files and configure deployment settings via the app in the latest version this should be a simple transition.
-
To take advantage of the new deployment configuration functionality
-
It is recommended that you delete all of your existing deployment pipeline variables except ServiceConnection and EnvironmentName and reconfigure your solutions for each target environment using the new deployment configuration functionality in the app.
-
Update your export-solution-to-git pipeline to include the following variable
-
Once you've updated the pipeline variable(s) go to the AA4AM App. Configure your solution deployment and export the solution to source control to ensure your deployment settings are stored appropriately in source control and the associated pipeline variables are created.
-
Change Log
- #301-Change how Connection References and Environment Variables are set to align with new Build Tools task
- #669-[AA4AM] Rename "global-variable-group" to make it easier to identify that it belongs to AA4AM
- #812-[ALM Accelerator - BUG]: Simplified Version Numbering
- #855-[AA4AM] Add deployment settings generator to Solution Export Pipeline
- #895-[AA4AM] Update Build Pipeline to use correct version of PAC CLI based on Canvas YAML version
- #924-export-solution-to-git pipeline error
- #938-[AA4AM] Solutions Not Updating When Environment Changes Automatically
- #954-[ALM Accelerator - BUG]: Custom Connector, GetIdentities unable to resolve schema
- #956-[AA4AM] September Release Documentation Updates
- #978-[AA4AM] Release Pipelines
- #1028-[CoE Starter Kit - Feature] Remove vnext branches
- #1051-[AA4AM] Add Ability to Configure Deployment Settings in Canvas App
- #1077-[AA4AM] Add support for latest version PAC CLI
- #1268-[AA4AM] Does not load connection references on config
CoE Starter Kit September 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/14
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
You will need to upgrade Core before you can update dependent solutions.
Please upgrade in the following order:
- Upgrade Core
- Upgrade Nurture
- Upgrade Gov
- Upgrade Audit Logs
If any of these do not work, keep that order but try to update instead of upgrade.
And if that still does not work, use classic UX to overwrite
Try to upgrade using the classic UX
Solution > Switch to Classic (note this can take some time, may have to try twice)
Click Import (fourth from the left)
Choose File (the solution file you were trying to install) > Next > Next >
Leave at Action=Upgrade but chose Overwrite customizations (note this is not the default) > Import
Change Log
- #425-[Core Components] Maker - Command Center
- #427-[Core Components] Admin - Command Center
- #973-[CoE Starter Kit - ENHANCEMENT] Add ability to monitor portals in the CoE inventory
- #976-[CoE Starter Kit - BUG] Sync Template v3 (Custom Connectors) doesn't get all Custom Connectors
- #977-[CoE Starter Kit - BUG] Warrington is back in the USA
- #986-[CoE Starter Kit - BUG] App Launch Trend in Power BI dashboard showing gaps
- #991-[CoE Starter Kit] Cleanup - Admin | Sync Template v3 (Check Deleted) hitting content throughput thresholds
- #1010-[CoE Starter Kit - QUESTION] Use Remove Flow as Admin in Governance flows
- #1019-[AA4AM] Update Release Pipelines to Use a CoE Bot Account
- #1022-[CoE Starter Kit - BUG] SharePoint Apps changing app id?
- #1026-[CoE Starter Kit - BUG] Developer Compliance Centre app - Not found segment 'annotations'
- #1032-[CoE Starter Kit - BUG] Cloud flow "Env Request | Create approved environment" doesn't work
- #1038-[CoE Starter Kit - Documentation request] add picture showing what is needed for Flow Approvals URL
- #1043-[CoE Starter Kit - BUG] DLP Editor V2 - Environment disappears on Remove from Policy
- #1050-Dataverse_CoEDashboard_202108.pbit errors on data refresh
- #1062-[CoE Starter Kit - BUG] Flows in solutions cannot be deleted by Archival flows - should warn user
- #1065-[CoE Starter Kit - BUG] Audit logs -- trouble with interval
- #1073-[CoE Starter Kit - BUG] If user manually deletes an app/flow, the table doesnt update deleted field
- #1081-[CoE Starter Kit - BUG] Set Flow Permissions app does not work for flows that are in a solution
- #1086-[AA4AM] - Simplify the use of Service Connections
- #1087-[CoE Starter Kit] Hide Content Conversion and Logic Flows from DLP Editor
- #1097-CoE Starter Kit: September release
- #1100-[CoE Starter Kit] All sync flows enabled by default except Sync Template (Flows)
- #1101-[CoE Starter Kit - BUG] Power Platform Request Center Error
- #1104-[CoE Starter Kit] Sync Flow (Apps) - store version number of app
- #1105-[CoE Starter Kit] Power BI report page for Environment Capacity
- #1111-[CoE Starter Kit - BUG] (Power Apps User Shared With) failing for user with Viral-GUID in role assignment return
- #1112-[AA4AM] Update Pipeline Sync Pipeline to Pull from Release Tag Commit
- #1113-[CoE Starter Kit - BUG] Missing Spatial Services Connector
- #1115-[CoE Starter Kit - BUG] Cloud flow Connections tab in Power BI report showing deleted Flows
- #1119-[CoE Starter Kit - BUG] - PBI Dashboard Not Displaying Custom Connectors Correctly
CoE Starter Kit August 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/11
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
In the August release, we have removed an old dependency that is no longer used, the CoE Settings table. Upgrade from July (or previous) solutions will need to proceed differently than normal as a result.
You have two options to successfully upgrade as a result.
Option 1: Changing the order of upgrade.
You will need to upgrade the dependent solutions before you upgrade Core. If possible, this is the preferred path.
Please upgrade in the following order:
Upgrade Nurture
Upgrade Gov
Update Audit Logs
Then upgrade Core
Option 2: Chose Update rather than Upgrade.
If you have dependencies from Core for these (aka if you are upgrading from older solutions). You may need to chose update instead. This will leave the CoE Settings in place, when you upgrade the other solutions, the dependency will remove, and your later upgrade (ex in September) will remove CoE Settings.
Instead of upgrade, use update to install Core August solutions.
As always, be sure to remove unmanaged layers in order to see our changes.
Change Log
- #402-[BUG]: CoE Theme Editor app, Publish Theme functionality is broken.
- #432-[Governance Components] Orphaned Resources and Archive Requests
- #434-[Core Components] Cloud Flow owners
- #438-[Core Components] Environment Request Management
- #553-[CoE Starter Kit - BUG]: Theme Publishing
- #731-[CoE Starter Kit] Process for working with orphaned resources
- #738-Add appid and flowid as columns on the entities
- #748-[CoE Starter Kit - Governance Components] Add summary email of deleted Teams environments to Admins
- #750-Documentation Request: Unpublished MDAs not surfaced.
- #752-Notification by mail of the flows and apps orphans.
- #789-[CoE Starter Kit - Documentation Request] Add RPA Size issue to Limitations list
- #800-[CoE Starter Kit - BUG] Edit Data option greyed out performing configure CoE settings table steps of core components installation
- #806-[CoE Starter Kit] Theming - new version is lower
- #807-[CoE Starter Kit - BUG] Core for Teams tables are not up to date with Core
- #810-[CoE Starter Kit - BUG] Power BI: Overview - Apps, Automate, Bots Top 20 environment count is incorrect
- #816-[CoE Starter Kit - BUG] - Connection Status flow failing due to deleted apps
- #822-[CoE Starter Kit - BUG] Legacy Power BI - Cloud flows issue with Creator filter
- #830-[CoE Starter Kit - BUG] Nurture - Feedback Reminder flow fails if no mail to send
- #831-[AA4AM] Reconfigure CoE Starter Kit Pipelines
- #833-[CoE Starter Kit - BUG] Remove dependency on CoE Settings Table
- #862-[CoE Starter Kit - Documentation BUG] HTTP with Azure AD connector for GCC High
- #868-[CoE Starter Kit - Documentation] Audit logs unclear how to respond to the "you need smaller chunks" mail
- #869-[CoE Starter Kit - BUG] Make link to Cleanup Old Objects App optional in the driving flow
- #870-[CoE Starter Kit - Test Case] Add Object ID as string to the views and Set Permissions apps for cloud flows, canvas apps, and MDAs
- #880-[CoE Starter Kit - BUG] PowerBI CDSLegacy July 2021 v2 defects
- #884-[CoE Starter Kit - BUG] Missing Fields in Power BI Dashboard for Dataverse for Teams
- #936-[CoE Starter Kit - BUG] if App is deleted manually by App Owner, it still sends reminder for the app backup to App Owner
- #942-[CoE Starter Kit - Documentation] update notes about env var as they imply solution already installed.
- #947-[CoE Starter Kit - Documentation] The caller with object id 'GUID' does not have permission for connection - add documentation on how to fix this co-auth issue
- #959-[CoE Starter Kit - BUG] Audit log solution: Invalid type. Expected String but got Null - ObjectId and UserKey
ALM Accelerator For Advanced Makers July 2021
[!IIMPORTANT] This release includes the use of an update in the platform that will not be released to the following geos (SPL, GCC, USG, CHN) until the last week in July. If you are using AA4AM in one of these geos please wait to upgrade until August 1st 2021.
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/10
First Time Setup Instructions
To get started with the ALM Accelerator For Advanced Makers you can
- Use the preview CoE CLI to automate the install at https://github.com/microsoft/coe-starter-kit/blob/main/coe-cli/docs/aa4am/readme.md or in the Power Platform CoE CLI E-Book
- Use the manual setup documentation can be found at https://github.com/microsoft/coe-starter-kit/blob/main/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md
Upgrade Instructions
If you are upgrading to the latest release you will need to perform the following steps.
-
Import the latest AA4AM Solution https://github.com/microsoft/coe-starter-kit/releases/download/ALMAcceleratorForAdvancedMakers-July2021/ALMAcceleratorForAdvancedMakers_1.0.20210727.1_managed.zip
-
Update your pipeline templates repo with the latest from https://github.com/microsoft/coe-alm-accelerator-templates
-
Export solutions with Canvas Apps using latest version of AA4AM.
[!NOTE] AA4AM use a preview version of the Power Apps Source File Pack and Unpack Utility (https://github.com/microsoft/PowerApps-Language-Tooling/blob/master/README.md). As such while AA4AM is still in public preview we are updating our pipelines to stay in sync with the latest releases of the Pack / Unpack utility. The Pack / Unpack utility is not backwards compatible while in preview meaning the version used to unpack must be the same as the version used to pack. If you have previously unpacked Canvas Apps using a previous version of AA4AM you will not be able to repack those apps. Therefore, you must export your solutions to source control again using the latest version so the formats match. We are planning on providing backward compatibility going forward after this release #895.
-
In this release we have updated the pipelines to allow for using a deployment configuration file stored in source control as an option rather than using Pipeline variables for the json configuration of Connection References, Component Ownership, App Sharing etc. There is a new doc included on how to setup your deployment configuration file and use variable substitution techniques to secure sensitive data from being source controlled. DEPLOYMENTCONFIGGUIDE.md.
[!NOTE] If you have previously configured your pipelines using pipeline variables you are not required to switch to using the deployment configuration file and the pipelines will continue to fall back to using pipeline variables in the absence of a deployment configuration file for the environment to which a solution is deployed. However, future updates to the Power Platform build tool will be reliant on a deployment configuration file so you may want to consider moving to this standard now.
-
The list of Azure DevOps extensions required for the AA4AM pipelines has been updated. Double check this list to ensure you have the correct extensions installed. Any extension that has been removed from the list can be safely removed Install Azure DevOps Extensions.
Change Log
- #27-[AA4AM] Pipelines: import-unmanaged-to-dev-environment - handle setting environment variables and connection references for empty environments
- #33-Setup automation based on the GETTINGSTARTED.md procedure
- #78-Custom Connector oauth settings break after Solution Import
- #115-Pipelines: Make Data Import Specific to Environment
- #121-Pipelines: Exclude Environment Variable Values from Source Control
- #122-AA4AM App: Update Solution Import Experience
- #123-AA4AM App: Update AA4AM User Role Permissions
- #331-[Documentation] Add App User Troubleshooting to SETUP doc
- #390-[AA4AM] Show environment banner in app
- #489-[AA4AM] Align Issue Templates for ALM Accelerators with CoE Starter Kit
- #513-[AA4AM] July Release Documentation Updates
- #523-[AA4AM] Replace temp-canvas-packager
- #560-[AA4AM] handle spaces in project name
- #561-[AA4AM] Add placeholder replacement to source controlled configuration
- #589-[AA4AM] Add Creation of GitHub Release to pipelines
- #596-[AA4AM] Replace RegEx Extension
- #600-[AA4AM]: Solution not appearing after import
- #607-[AA4AM] Export Solution to Git error
- #616-[AA4AM]: Wiping out connections json is causing errors on solution deployment
- #635-[ALM Accelerator - BUG]: Default Branch May Not Be
mainWhen Cloning Pipelines - #636-[ALM Accelerator - BUG]: Setup Documentation Sequencing - Create Pipeline Global Variables before Service Connections Created
- #643-Prod template references Validation in comment
- #697-[AA4AM]: Check Default Value of specified environment variables
- #698-[AA4AM]: Check no current value is present for environment variables on release
- #706-[ALM Accelerator - BUG]: Error at the build-deploy "pack msapp files" step
- #785-[AA4AM] Creating a Release should close and comment on completed items
- #802-[ALM Accelerator - BUG]: Update Solution Component Ownership Failed
- #844-[AA4AM] - Make docs more clear that we're in public preview
CoE Starter Kit July 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/8
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Change Log
- #769-CoE Starter Kit: Core for Teams July release
- #767-CoE Starter Kit - Audit Logs: July Release
- #766-CoE Starter Kit - Nurture Components: July Release
- #739-Pushing the latest Theming solution to main
- #735-[CoE Starter Kit] Add Power BI embedded apps to Core Components solution
- #730-[CoE Starter Kit] Connector - Product Owner
- #725-[CoE Starter Kit - BUG] Desktop Flows sync flow fails at Parse RPA JSON step
- #699-[CoE Starter Kit Bug]: Flow Action Details Sync flow incorrectly evaluating FullInventory value
- #695-[CoE Starter Kit - Nurture] Training in a day registration shows past events
- #682-[CoE Starter Kit - BUG]: Gov Flows are sending to end user
- #670-[CoE Starter Kit - BUG]: Set Flow/Apps Permissions shows owners withouts apps/flows
- #661-[CoE Starter Kit - BUG]: Error Creating a new DPL Policie using DLP Editor v2 App
- #660-[CoE Starter Kit - Enhancement]: Tell admin when they need to change interval to get all the audit logs
- #658-[CoE Starter Kit - Enhancement]: Update Audit Log solution to be configurable through environemnt variables
- #655-Exporting latest of theming solution
- #654-[CoE Starter Kit - BUG]: Theming Solution Re-export
- #644-steps to set default branch on import repo #635
- #640-Power BI Center of Excellence Dashboard - Connector Usage Validation Issue
- #627-[CoE Starter Kit - BUG]: Developer Compliance Center - Delete App Error
- #621-[CoE Starter Kit - BUG]: Set XX Owner App: some users showing without name/image
- #614-[Set Flow Permissions] Url incomplete to access to Flow settings
- #611-[CoE Starter Kit - BUG]: Power BI Dashboard - Cloud Flow filtering by Connectors and Flow Actions does not work
- #606-[CoE Starter Kit - BUG]: DLP Editor Impact Analysis "x of [apps]" shows incorrect number
- #605-[CoE Starter Kit - BUG]: Unable to search by environment in the DLP Editor V2 canvas app
- #604-DLP V2 Editor - Order the connectors by name alphabetically on the Assign connector page
- #603-[Core] Admin | Sync Template v3 (Flows) - Did not check for owner existing when setting Derived Owner
- #595-[CoE Starter Kit - BUG]: No impact analysis results being shown anymore in the DLP Editor V2 app
- #594-[CoE Starter Kit - BUG]: Dataverse Connectors can be moved to blocked with DLP Editor V2 Canvas App
- #558-[Core Components] Include Power BI embedded apps in solution
- #555-[Core Components] Power BI - change to Star Schema
CoE Starter Kit - June 2021
Issues and new features in this release:
https://github.com/microsoft/coe-starter-kit/milestone/7
First Time Setup Instructions
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrade Instructions
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
ALM Accelerator For Makers 1.0.20210521.1
Latest release of source code for the ALM Accelerator For Makers.
First Time Setup Instructions
To get started with the ALM Accelerator For Makers the setup documentation can be found at https://docs.microsoft.com/en-us/power-platform/guidance/coe/almaccelerator-components
Upgrade Instructions
If you are upgrading to the latest release you will need to perform the following steps. NOTE: We've changed the internal name of the AA4M Solution in this release.
- Import the latest AA4M Solution https://github.com/microsoft/coe-starter-kit/releases/download/ALMAcceleratorForMakers-1.0.20210521.1/ALMAcceleratorForMakers_1.0.20210521.1_managed.zip
- Delete the Existing managed solution with the schema name PowerPlatformGitHubALM
ALM Accelerator For Advanced Makers 1.0.20210521.1
Public preview release of the ALM Accelerator For Advanced Makers. Included in this release are the following enhancements/fixes.
First Time Setup Instructions
To get started with the ALM Accelerator For Advanced Makers check out the ReadMe )https://github.com/microsoft/coe-starter-kit/blob/main/PowerPlatformDevOpsALM/README.md) and Setup Guide (https://github.com/microsoft/coe-starter-kit/blob/main/PowerPlatformDevOpsALM/SETUPGUIDE.md)
Upgrade Instructions
If you are upgrading to the latest public preview you will need to perform the following steps. NOTE: We've changed the internal name of the AA4AM Solution in this release. As a result you will need to delete the existing solution which will cause your App Settings to reset and you'll need to reconfigure.
- Delete the Existing managed solution with the schema name PowerPlatformDevOpsALM
- Import the latest AA4AM Solution https://github.com/microsoft/coe-starter-kit/releases/download/AA4AM-1.0.20210521.1/ALMAcceleratorForAdvancedMakers_1.0.20210521.1_managed.zip
- Update your pipeline templates repo with the latest from https://github.com/microsoft/coe-alm-accelerator-templates
- We have created a new pipeline to make updating of your Azure DevOps Pipeline Templates simpler going forward. The pipeline can be run manually inside of your Azure DevOps project and will download the latest templates for you and create a Pull Request into your Pipeline Template repo for you to merge any changes. For more information see here https://github.com/microsoft/coe-starter-kit/blob/ALMAcceleratorForAdvancedMakers/ALMAcceleratorForAdvancedMakers/PIPELINESYNCGUIDE.md
- Update Custom Connector Authentication https://github.com/microsoft/coe-starter-kit/blob/ALMAcceleratorForAdvancedMakers/ALMAcceleratorForAdvancedMakers/SETUPGUIDE.md#configure-the-azure-devops-custom-connector
Issues Addressed in this Release:
- Load more than the first 100 ADO projects per org #399
- Update Internal Name of ALM Accelerator Solutions #359
- Remove multiple agents for build/deploy #417
- Remove ValidationServiceConnection as Global Variable #381
- Pipelines: Overwrite Unmanaged Customizations On Import #231
- AA4AM App: Update Solution Import Experience #122
- Pipelines: GitHub treating json files as bin #368
- AA4AM: Has Deleted Solution Components and subsequent commits #192
NOTE to Private Preview Members: In this release we made the decision to remove the build-deploy-Solution pipeline that was available in Private Preview in favor of the new environment specific pipelines. Up until the previous release we were still supporting the old multi-stage pipeline, but it was causing us to have to put in a lot of workarounds to keep supporting it.
The benefit of the new environment specific pipelines is you can set them up for as many or as few environments as you like and you can also trigger production deployments without a build which will deploy the latest solution from the test pipeline instead of building again