Conversation
Validation failed!File: samples/m365-copilot-software-request-tracker/assets/sample.json
|
Contributor
Author
|
Please let me know if you need anything from me. I tried to verify that validation, but I don't see the URL it's referencing. Thanks, Andrew |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This prompt helps IT managers and infrastructure teams track the lifecycle of software acquisition requests across email and Teams communications. It automatically identifies software titles mentioned in the past 12 months, extracts the date of first request, summarizes current approval status, flags outstanding tasks or concerns, and highlights requests involving key contacts (e.g., vendorchecklist@yourcompany.com or mrprocurement@yourcompany.com). It also assesses each software’s security maturity, checks for SOC reports, and verifies AI-related data privacy documentation. The output is a structured report grouped by software title, designed to run on a recurring schedule (e.g., every Monday and Wednesday at 7 AM) to keep stakeholders informed and aligned.