One of the key use cases that we see across every industry and every department are approvals. Power Automate allows you to streamline your business by digitalizing the approval experience.
“Business approvals kit” – is a kit that will accelerate building your approvals faster than ever - available as an experimental preview. Business approvals kit is a no-code ready-made template built on top of Power Platform components that allows your organization to configure sophisticated approvals such as conditional branching, delegation, admin overrides and more – all without the need to write a single code – empowering every person in your organization to "do more with less" for your organizations approval needs.
Review regular office hours to join monthly hours to review new features, roadmap and question and answer session.
The Business Approvals kit GitHub Repo contains the source, releases, issues and backlog items of all components that are part of the Business Approvals kit.
The latest shipped version is available via Releases. From there, you can download the latest version of all managed solutions that have been tested and are ready for use.
Stay up to date with our releases by subscribing to them:
- Select Watch
- Select Custom > Releases > Apply to receive notifications about our releases
Have you found a bug in the Business Approvals kit or do you want to suggest a new feature? Either way, please let us now by filing an issue while observing the following guidelines
Before submitting your issue please search the issues to ensure your issue has not already been reported
If your bug or feature request has already been reported, join the conversation by commenting and adding your reaction. Please use reactions to vote and not "+1" comments.
- 👍 - upvote
- 👎 - downvote
Select the Issue template that matches the solution for which you want to submit an issue.
File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue.
Do not add your issue as a comment to an existing issue unless it's for the identical input. Many issues look similar, but have different causes.
The more information you can provide, the more likely someone will be successful at reproducing the issue and finding a fix.
Observe the inline guidelines of the Issue template.
Join the discussions and ask your question or contribute by answering questions from others. This is a great way to contribute by helping the CoE Starter Kit community.
If you have general questions about Power Automate approval connectors, unrelated to the Business Approvals kit, please raise them in the Power Automate Community forum
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.
When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
This project has adopted the Microsoft Open Source Code of Conduct.
Resources:
- Microsoft Open Source Code of Conduct
- Microsoft Code of Conduct FAQ
- Contact opencode@microsoft.com with questions or concerns
This project may contain trademarks or logos for projects, products, or services. Authorized use of Microsoft trademarks or logos is subject to and must follow Microsoft's Trademark & Brand Guidelines. Use of Microsoft trademarks or logos in modified versions of this project must not cause confusion or imply Microsoft sponsorship. Any use of third-party trademarks or logos are subject to those third-party's policies.
Please do not report security vulnerabilities through public GitHub issues.
Instead, please report them to the Microsoft Security Response Center (MSRC) at https://msrc.microsoft.com/create-report.
If you prefer to submit without logging in, send email to secure@microsoft.com. If possible, encrypt your message with our PGP key; please download it from the the Microsoft Security Response Center PGP Key page.
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your original message. Additional information can be found at microsoft.com/msrc.
Please include the requested information listed below (as much as you can provide) to help us better understand the nature and scope of the possible issue:
- Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.)
- Full paths of source file(s) related to the manifestation of the issue
- The location of the affected source code (tag/branch/commit or direct URL)
- Any special configuration required to reproduce the issue
- Step-by-step instructions to reproduce the issue
- Proof-of-concept or exploit code (if possible)
- Impact of the issue, including how an attacker might exploit the issue
This information will help us triage your report more quickly.
If you are reporting for a bug bounty, more complete reports can contribute to a higher bounty award. Please visit our Microsoft Bug Bounty Program page for more details about our active programs.
We prefer all communications to be in English.
Microsoft follows the principle of Coordinated Vulnerability Disclosure.