Bot releases are hidden (Show)
Published by Jenefer-Monroe about 1 month ago
https://github.com/microsoft/coe-starter-kit/issues/8917 [CoE Starter Kit - QUESTION] Where are Flow details page links stored?
https://github.com/microsoft/coe-starter-kit/issues/8954 Admin | Audit Logs | Sync Audit Logs (V2) hard coded to graph for new graph api version
https://github.com/microsoft/coe-starter-kit/issues/8881 [CoE Starter Kit - BUG] Power BI - Flow Deep Dive Does Not Filter
https://github.com/microsoft/coe-starter-kit/issues/8916 Setup Wizard and Command Center failing to set env vars
https://github.com/microsoft/coe-starter-kit/issues/8956 Create version of Core without the PPAdmin V2 connector for Sovereign cloud users
Published by Jenefer-Monroe about 1 month ago
Published by Jenefer-Monroe 2 months ago
Note that there was a COGS escalation and it was found that we had debug code in the Admin | Sync Template v4 (AI Events) flow which caused us to process 45 days worth of AI Events each day. So we had to recreate Core to resolve this.
Please see https://github.com/microsoft/coe-starter-kit/issues/8814
New version of Core is now 4.37
https://github.com/microsoft/coe-starter-kit/issues/8549 [CoE Starter Kit - QUESTION] Deleting Solution Aware Flows in CoE
https://github.com/microsoft/coe-starter-kit/issues/8573 [CoE Starter Kit - BUG] Blogs in CoE Admin Command App
https://github.com/microsoft/coe-starter-kit/issues/8607 [CoE Starter Kit - BUG] Update naming convention DLP > Data Policies
https://github.com/microsoft/coe-starter-kit/issues/8611 Error on load admin command center bookmarks page: The value 'Preview builds for testing' cannot be converted to a date or time value
https://github.com/microsoft/coe-starter-kit/issues/8612 [CoE Starter Kit - BUG] ISSUE TITLE Admin | Newsletter with Product Updates flow, List Flow Blog RSS feed items fails
https://github.com/microsoft/coe-starter-kit/issues/8626 [CoE Starter Kit - BUG] Comments doesn't work when enabled along with Related videos
https://github.com/microsoft/coe-starter-kit/issues/8627 Fix reference to "preview" in command center support page
https://github.com/microsoft/coe-starter-kit/issues/8644 Maker Environment Request App - Least Privilege Security Principle
https://github.com/microsoft/coe-starter-kit/issues/8668 [CoE Starter Kit - BUG] AI Credits Usage table not added to CoE SR's
https://github.com/microsoft/coe-starter-kit/issues/8683 [CoE Starter Kit - BUG] Get_toWhom_profileo issue with the "Assign to all" button in the Request Orphaned Objects Reassigned (Child) flow
https://github.com/microsoft/coe-starter-kit/issues/8692 App Catalog and search bug
https://github.com/microsoft/coe-starter-kit/issues/8697 [CoE Starter Kit - BUG] Wrong email sent to managers from Orphaned Objects "Email Me" option
https://github.com/microsoft/coe-starter-kit/issues/8711 [CoE Starter Kit - QUESTION] governance flows - import as disabled
https://github.com/microsoft/coe-starter-kit/issues/8724 [CoE Starter Kit - BUG] Maker Not Notified of Rejected Environment Request - Flow "Env Request | Notify requestor when rejected" Not Triggered
https://github.com/microsoft/coe-starter-kit/issues/8728 Failure in CLEANUP - Admin | Sync Template v3 (Orphaned Users) when cannot get tenant count
https://github.com/microsoft/coe-starter-kit/issues/8738 [CoE Starter Kit - BUG] Manage Permissions App fails when trying to delete orphaned flows
https://github.com/microsoft/coe-starter-kit/issues/8741 Environment Capacity for no Dataverse environment doesn't have capacity
https://github.com/microsoft/coe-starter-kit/issues/8776 [CoE Starter Kit - BUG] Video thumbnails not showing in MDA Video Hub New
https://github.com/microsoft/coe-starter-kit/issues/8729 Admin | Sync Template v4 (AI Events) failing - some users azureid not listed
https://github.com/microsoft/coe-starter-kit/issues/8814 Admin | Sync Template v4 (AI Events) consuming too many api calls due to debug code left in call
https://github.com/microsoft/coe-starter-kit/issues/8809 [CoE Starter Kit - QUESTION] Fix up spots that still have the removed "Total Shared With" field
https://github.com/microsoft/coe-starter-kit/issues/8016 [CoE Starter Kit - Feature]: Update Kit to respond to new Power Platform Admin Role PIM feature
https://github.com/microsoft/coe-starter-kit/issues/8481 [CoE Starter Kit - Feature]: BVA Setup Wizard screen and Metadata integration
https://github.com/microsoft/coe-starter-kit/issues/8482 [CoE Starter Kit - Feature]: Integrate new audit log methodology into the kit for API reduction
https://github.com/microsoft/coe-starter-kit/issues/8565 [CoE Starter Kit - Feature]: Automated Install Roadmap
https://github.com/microsoft/coe-starter-kit/issues/8591 [CoE Starter Kit - Feature]: Automated Install - Setup Wizard - Connection consent
https://github.com/microsoft/coe-starter-kit/issues/8701 Add new TeamsWebhook specialty connector to the kit
https://github.com/microsoft/coe-starter-kit/issues/8716 [CoE Starter Kit - Feature]: PBI Dashboards - Production_CoEDashboard - Flow Deep Dive Page
https://github.com/microsoft/coe-starter-kit/issues/8752 PIM - only record escalation error after checking
Published by Jenefer-Monroe 3 months ago
Because Core is too big to share in comments will put bits here for testing.
Current test build is the July 2024 release plus fixes to these two issues:
https://github.com/microsoft/coe-starter-kit/issues/8016 - Update Kit to respond to new Power Platform Admin Role PIM feature
https://github.com/microsoft/coe-starter-kit/issues/8482 - Integrate new audit log methodology into the kit for API reduction
Please look at issues for setup / testing instructions.
Published by RajeevPentyala over 1 year ago
Published by RajeevPentyala over 1 year ago
Published by manuelap-msft over 1 year ago
https://github.com/microsoft/coe-starter-kit/issues/5595- [CoE Starter Kit - BUG] Wrong Environment ID for Default Environment Sync
Published by manuelap-msft over 1 year ago
https://github.com/microsoft/coe-starter-kit/issues/5331 - [CoE Starter Kit - BUG] CLEANUP HELPER - Check Deleted (Cloud Flows) marking existing Flows as deleted
Published by mikefactorial almost 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/21?closed=1
Run the Admin | Sync Template v3 Configure Emails flow after import to pre-populate default values for all emails.
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/after-setup
Published by mikefactorial almost 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/20?closed=1
The way email body and subject are configured changed with this release. You need to run the Admin | Sync Template v3 Configure Emails flow after import to pre-populate default values for all emails.
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Published by mikefactorial almost 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/18?closed=1
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Published by mikefactorial about 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/13?closed=1
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).
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
To get started with the ALM Accelerator For Advanced Makers you can
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.
Published by mikefactorial about 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/17
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Published by mikefactorial about 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/14
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
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:
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
Published by mikefactorial about 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/11
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
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.
Published by mikefactorial about 3 years ago
[!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.
https://github.com/microsoft/coe-starter-kit/milestone/10
To get started with the ALM Accelerator For Advanced Makers you can
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.
main
When Cloning PipelinesPublished by mikefactorial over 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/8
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Published by manuelap-msft over 3 years ago
https://github.com/microsoft/coe-starter-kit/milestone/7
Get started with the CoE Starter Kit Setup: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup
Upgrading from the latest version: https://docs.microsoft.com/en-us/power-platform/guidance/coe/setup#installing-updates
Published by mikefactorial over 3 years ago
Latest release of source code for the ALM Accelerator For Makers.
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
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.
Published by mikefactorial over 3 years ago
Public preview release of the ALM Accelerator For Advanced Makers. Included in this release are the following enhancements/fixes.
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)
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.
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