Skip to content

microsoft/Federal-Business-Applications

Repository files navigation

US Government Business Applications Demo Repository

Welcome to the US Government Business Applications Demo Repository. This repository was created to showcase sample solutions that run in the Power Platform and Dynamics 365 in our various US sovereign government clouds.

US Federal Biz Apps Logo

Demos

Below is a listing of the sample solutions available. These sample solution files are meant for demonstration purposes only to quickly showcase various features across our platform.

Demo Name GCC GCC High DoD
Access Data Migration to Dataverse ✔️
AI Builder Drivers License Canvas App ✔️ ✔️
AI Builder Form Processing + RPA ✔️ ✔️
Azure Computer Vision Canvas App ✔️ ✔️ ✔️
Book a Room Template App ✔️ ✔️
Chargeback & License Management ✔️ ✔️ ✔️
Dynamics 365 Fraud Protection ✔️ ✔️ ✔️
Dynamics 365 or Model-Driven Power Apps & Teams Click-To-Dial ✔️
DevOps with GitHub Actions ✔️ ✔️ ✔️
Electronic Signature Canvas App ✔️ ✔️ ✔️
Mixed Reality - Take Measurements Demo ✔️
govDelivery Custom Connector ✔️ ✔️ ✔️
Electronic Signature PDF Flow ✔️
PII Redaction with Power Automate ✔️ ✔️
Populating Dataverse with ArcGIS Data Using Power Automate ✔️ ✔️ ✔️
Power Query Custom Data Connector for Power Automate REST APIs ✔️
Power Query Custom Data Connector for Power BI REST APIs ✔️
PowerShell Gov Samples ✔️ ✔️ ✔️
Return to the Workplace ✔️ ✔️ ✔️
RPA Web Scraping Demo ✔️ ✔️ ✔️
Rules Engine ✔️ ✔️ ✔️
Transcript Demo: Power Platform + Azure Speech to Text ✔️
Vaccine Attestation ✔️ ✔️ ✔️

Whitepapers

Accessibility and Section 508 Conformance

Power Platform

Below are whitepapers that have been created specifically for use in the US Government sovereign cloud regions.

Power BI

Webinar Series

We recently launched a new Federal Business Applications webinar series. Past recordings and future session details can be found below,

Federal Forums

Training Resources

Power Apps / Power Automate

Dynamics 365

Power BI

Contributing

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 repositories 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.

Contributing Guidelines

For non-Microsoft employees, you can fork this repository, and then submit any contributions with a pull request. Someone on the contributors team will review your pull request and then work to get it merged into the repository. Details on how to fork this repository and submit a pull request are available on GitHub's documentation page below,

Creating a Pull Request from a Fork

Spell Check

We also have spell checking enabled via a GitHub Action. To see if you have any spelling typos, run the Spellcheck Action associate with this repository. We also have a file that contains a list of spell check exceptions. You may need to add acronyms or other words to this list as you run into them.

Spell Check Word List

Folder Naming Conventions

If you want to add a new demo or whitepaper, follow the folder structure convention below,

demos/
├─ your-new-demo-folder/
│  ├─ files/
│  │  ├─ image1.PNG
│  │  ├─ image2.PNG
│  │  ├─ sampleSolution.zip
│  ├─ README.md
whitepapers/
├─ your-new-whitepaper-folder/
│  ├─ files/
│  │  ├─ image1.PNG
│  ├─ README.md
├─ your-new-whitepaper2-folder/
│  ├─ summary.pdf
README.md

You can decide if you would rather have a README.md file with Markdown syntax, or if you prefer, you can convert a document into a PDF file and then upload that into the subfolder for the demo/whitepaper. PDF's will render in the browser when viewed on GitHub. README.md files are preferred as they will also support version control and change history on the actual file.

Lastly, link from this main README.md page to your new demo/whitepaper and the corresponding README.md or PDF file.

Trademarks

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.