[Feature Request] Post Intune App Factory packaging information to a Teams Channel

[AScott-WWF]

This is a feature improvement request for Intune App Factory, to allow us to be notified via a Teams Channel when a new version of an application has been packaged, rather than just noticing a new version has appeared in the Pipeline / or In the Intune Application list

Here are a couple of links that may help
https://learn.microsoft.com/en-us/azure/devops/pipelines/integrations/microsoft-teams?view=azure-devops
https://learn.microsoft.com/en-us/azure/devops/service-hooks/services/teams?view=azure-devops

Initially we would like to post a message to a channel to include information such as

• Application Name
• Version
• Release Date (Could be obtained from Evergreen (Date or StartDate in some cases) or fails back to the date Intune App Factory detects it as new)
• Release Notes *
• Who the App has been deployed to (i.e. Entra ID Group Name)

Eventually we could hope to include an approval process here too, which could change the group assignments
Unsure where in the Intune App Factory Pipeline we should configure this.

* Release Notes and how they are published vary from vendor to vendor, but are useful to guide packagers as they guide us as to whether the version contains security fixes so will raise the priority an app should be deployed.
I have a number of scripts currently that programatically determine and then open the correct release notes for the current version
All my scripts populate a $LatestVersion variable with the latest version from either Evergreen, NeverGreen or Webscrape and can then be reused throughout the script, so for example the Firefox release notes are available via this:
$ReleaseNotesURL = "https://www.mozilla.org/en-US/firefox/$($LatestVersion)/releasenotes/"
Therefore the $ReleaseNotesURL could be included as a link within the message to the Teams Channel

I'd be more than happy to share my Release Notes URLs (or the programaticly determined URL) for the various apps we have as this could be useful for others too.
From a design descision I think these could either reside within the (master) AppList.json or within the specific App's App.json