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.

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.

• Section 508 Conformance
• Federal Business Applications Webinar - Accessibility - March 2022

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

• Power Platform / Dynamics 365 Gov Architecture
• Power Platform / Dynamics 365 Federal Security Recommendations
• Power Platform / Dynamics 365 Copilot Resources
• Azure Synapse Link Integration
• Consume Commercial Azure Storage Resources from Power Platform GCC
• Creating US Government Support Tickets
• Enable Azure AD Connector in GCC
• How to use the O365 Outlook Connector for Notifications
• Power Apps Developer Plan for US Government Customers
• Power Virtual Agents and Power BI in US Gov Clouds
• Power Apps - 'Add App to Teams' Workaround for GCC

• Power BI Desktop Registry Settings for US Gov Clouds
• Power BI & O365 Forms Integration in US Gov Clouds
• Power BI Visuals Download Tool
• A Guide to Power BI Embedding within Government Community Clouds (GCC)

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

• Federal Business Applications Webinar Sessions

• Federal App Makers Forum

• App in a Day
• RPA in a Day
• Power Platform Learning Paths
• Power Platform Center of Excellence Starter Kit
• Power CAT Adoption Maturity Model
• AI Builder Labs

• Dynamics 365 Learning Paths
• Dynamics 365 Certifications

• Power BI Learning Paths
• Guy in a Cube YouTube Channel
• Power BI Training Content
• Power BI Dashboard in an Hour Lab
• Power BI Paginated Reports in a Day YouTube Training
• Power BI Adoption Framework

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.

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

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

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.

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.