├── .gitignore ├── CODE_OF_CONDUCT.md ├── CONTRIBUTING.md ├── LICENSE ├── README.md ├── SECURITY.md ├── WindowsVirtualDesktop ├── README.MD └── WindowsVirtualDesktop.zip ├── azuregovernance ├── AzureGovernance.zip ├── README.MD ├── docs │ ├── Azure_Cloud_Architecture-Shared-BusinessUnit-Model-Sample_V1.vsdx │ ├── Azure_Management-Subscription-Architecture-Sample-v1.vsdx │ ├── Azure_Networking_Cloud_Architecture_Sample_v1.vsdx │ ├── CAF-Azure_Account_Organization_and_Governance.pptx │ ├── CAF-Cloud_Adoption_Framework_Overview.pptx │ ├── CAF_Governance_Playbook V2.docx │ ├── Cloud_Adoption_Framework_One_Pager.pdf │ ├── Enterprise-Scale-Architecture.vsdx │ ├── Governance_Implementation_Matrix_v1.xlsx │ └── ps-cli-scripts │ │ ├── RG-Tag-Template.cli │ │ ├── RG-Tag-Template.ps1 │ │ ├── RG-Tag-Template.txt │ │ ├── RG-Tag-Template.zip │ │ └── a └── pictures │ ├── azcommunity.png │ ├── caf.png │ ├── createproject.png │ └── governance.png ├── azuresentinel ├── AzureSentinelDevopsBoardTemplate.zip └── README.MD ├── caf.png └── nist800171Rev2 ├── Customer Reponsiblity Matrix - NIST 800-171.xlsx ├── NIST 800-171 Compliance as a Service.pdf ├── NIST800171Rev2.zip └── README.MD /.gitignore: -------------------------------------------------------------------------------- 1 | ## Ignore Visual Studio temporary files, build results, and 2 | ## files generated by popular Visual Studio add-ons. 3 | ## 4 | ## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore 5 | 6 | # User-specific files 7 | *.rsuser 8 | *.suo 9 | *.user 10 | *.userosscache 11 | *.sln.docstates 12 | 13 | # User-specific files (MonoDevelop/Xamarin Studio) 14 | *.userprefs 15 | 16 | # Mono auto generated files 17 | mono_crash.* 18 | 19 | # Build results 20 | [Dd]ebug/ 21 | [Dd]ebugPublic/ 22 | [Rr]elease/ 23 | [Rr]eleases/ 24 | x64/ 25 | x86/ 26 | [Aa][Rr][Mm]/ 27 | [Aa][Rr][Mm]64/ 28 | bld/ 29 | [Bb]in/ 30 | [Oo]bj/ 31 | [Ll]og/ 32 | [Ll]ogs/ 33 | 34 | # Visual Studio 2015/2017 cache/options directory 35 | .vs/ 36 | # Uncomment if you have tasks that create the project's static files in wwwroot 37 | #wwwroot/ 38 | 39 | # Visual Studio 2017 auto generated files 40 | Generated\ Files/ 41 | 42 | # MSTest test Results 43 | [Tt]est[Rr]esult*/ 44 | [Bb]uild[Ll]og.* 45 | 46 | # NUnit 47 | *.VisualState.xml 48 | TestResult.xml 49 | nunit-*.xml 50 | 51 | # Build Results of an ATL Project 52 | [Dd]ebugPS/ 53 | [Rr]eleasePS/ 54 | dlldata.c 55 | 56 | # Benchmark Results 57 | BenchmarkDotNet.Artifacts/ 58 | 59 | # .NET Core 60 | project.lock.json 61 | project.fragment.lock.json 62 | artifacts/ 63 | 64 | # StyleCop 65 | StyleCopReport.xml 66 | 67 | # Files built by Visual Studio 68 | *_i.c 69 | *_p.c 70 | *_h.h 71 | *.ilk 72 | *.meta 73 | *.obj 74 | *.iobj 75 | *.pch 76 | *.pdb 77 | *.ipdb 78 | *.pgc 79 | *.pgd 80 | *.rsp 81 | *.sbr 82 | *.tlb 83 | *.tli 84 | *.tlh 85 | *.tmp 86 | *.tmp_proj 87 | *_wpftmp.csproj 88 | *.log 89 | *.vspscc 90 | *.vssscc 91 | .builds 92 | *.pidb 93 | *.svclog 94 | *.scc 95 | 96 | # Chutzpah Test files 97 | _Chutzpah* 98 | 99 | # Visual C++ cache files 100 | ipch/ 101 | *.aps 102 | *.ncb 103 | *.opendb 104 | *.opensdf 105 | *.sdf 106 | *.cachefile 107 | *.VC.db 108 | *.VC.VC.opendb 109 | 110 | # Visual Studio profiler 111 | *.psess 112 | *.vsp 113 | *.vspx 114 | *.sap 115 | 116 | # Visual Studio Trace Files 117 | *.e2e 118 | 119 | # TFS 2012 Local Workspace 120 | $tf/ 121 | 122 | # Guidance Automation Toolkit 123 | *.gpState 124 | 125 | # ReSharper is a .NET coding add-in 126 | _ReSharper*/ 127 | *.[Rr]e[Ss]harper 128 | *.DotSettings.user 129 | 130 | # TeamCity is a build add-in 131 | _TeamCity* 132 | 133 | # DotCover is a Code Coverage Tool 134 | *.dotCover 135 | 136 | # AxoCover is a Code Coverage Tool 137 | .axoCover/* 138 | !.axoCover/settings.json 139 | 140 | # Visual Studio code coverage results 141 | *.coverage 142 | *.coveragexml 143 | 144 | # NCrunch 145 | _NCrunch_* 146 | .*crunch*.local.xml 147 | nCrunchTemp_* 148 | 149 | # MightyMoose 150 | *.mm.* 151 | AutoTest.Net/ 152 | 153 | # Web workbench (sass) 154 | .sass-cache/ 155 | 156 | # Installshield output folder 157 | [Ee]xpress/ 158 | 159 | # DocProject is a documentation generator add-in 160 | DocProject/buildhelp/ 161 | DocProject/Help/*.HxT 162 | DocProject/Help/*.HxC 163 | DocProject/Help/*.hhc 164 | DocProject/Help/*.hhk 165 | DocProject/Help/*.hhp 166 | DocProject/Help/Html2 167 | DocProject/Help/html 168 | 169 | # Click-Once directory 170 | publish/ 171 | 172 | # Publish Web Output 173 | *.[Pp]ublish.xml 174 | *.azurePubxml 175 | # Note: Comment the next line if you want to checkin your web deploy settings, 176 | # but database connection strings (with potential passwords) will be unencrypted 177 | *.pubxml 178 | *.publishproj 179 | 180 | # Microsoft Azure Web App publish settings. Comment the next line if you want to 181 | # checkin your Azure Web App publish settings, but sensitive information contained 182 | # in these scripts will be unencrypted 183 | PublishScripts/ 184 | 185 | # NuGet Packages 186 | *.nupkg 187 | # NuGet Symbol Packages 188 | *.snupkg 189 | # The packages folder can be ignored because of Package Restore 190 | **/[Pp]ackages/* 191 | # except build/, which is used as an MSBuild target. 192 | !**/[Pp]ackages/build/ 193 | # Uncomment if necessary however generally it will be regenerated when needed 194 | #!**/[Pp]ackages/repositories.config 195 | # NuGet v3's project.json files produces more ignorable files 196 | *.nuget.props 197 | *.nuget.targets 198 | 199 | # Microsoft Azure Build Output 200 | csx/ 201 | *.build.csdef 202 | 203 | # Microsoft Azure Emulator 204 | ecf/ 205 | rcf/ 206 | 207 | # Windows Store app package directories and files 208 | AppPackages/ 209 | BundleArtifacts/ 210 | Package.StoreAssociation.xml 211 | _pkginfo.txt 212 | *.appx 213 | *.appxbundle 214 | *.appxupload 215 | 216 | # Visual Studio cache files 217 | # files ending in .cache can be ignored 218 | *.[Cc]ache 219 | # but keep track of directories ending in .cache 220 | !?*.[Cc]ache/ 221 | 222 | # Others 223 | ClientBin/ 224 | ~$* 225 | *~ 226 | *.dbmdl 227 | *.dbproj.schemaview 228 | *.jfm 229 | *.pfx 230 | *.publishsettings 231 | orleans.codegen.cs 232 | 233 | # Including strong name files can present a security risk 234 | # (https://github.com/github/gitignore/pull/2483#issue-259490424) 235 | #*.snk 236 | 237 | # Since there are multiple workflows, uncomment next line to ignore bower_components 238 | # (https://github.com/github/gitignore/pull/1529#issuecomment-104372622) 239 | #bower_components/ 240 | 241 | # RIA/Silverlight projects 242 | Generated_Code/ 243 | 244 | # Backup & report files from converting an old project file 245 | # to a newer Visual Studio version. Backup files are not needed, 246 | # because we have git ;-) 247 | _UpgradeReport_Files/ 248 | Backup*/ 249 | UpgradeLog*.XML 250 | UpgradeLog*.htm 251 | ServiceFabricBackup/ 252 | *.rptproj.bak 253 | 254 | # SQL Server files 255 | *.mdf 256 | *.ldf 257 | *.ndf 258 | 259 | # Business Intelligence projects 260 | *.rdl.data 261 | *.bim.layout 262 | *.bim_*.settings 263 | *.rptproj.rsuser 264 | *- [Bb]ackup.rdl 265 | *- [Bb]ackup ([0-9]).rdl 266 | *- [Bb]ackup ([0-9][0-9]).rdl 267 | 268 | # Microsoft Fakes 269 | FakesAssemblies/ 270 | 271 | # GhostDoc plugin setting file 272 | *.GhostDoc.xml 273 | 274 | # Node.js Tools for Visual Studio 275 | .ntvs_analysis.dat 276 | node_modules/ 277 | 278 | # Visual Studio 6 build log 279 | *.plg 280 | 281 | # Visual Studio 6 workspace options file 282 | *.opt 283 | 284 | # Visual Studio 6 auto-generated workspace file (contains which files were open etc.) 285 | *.vbw 286 | 287 | # Visual Studio LightSwitch build output 288 | **/*.HTMLClient/GeneratedArtifacts 289 | **/*.DesktopClient/GeneratedArtifacts 290 | **/*.DesktopClient/ModelManifest.xml 291 | **/*.Server/GeneratedArtifacts 292 | **/*.Server/ModelManifest.xml 293 | _Pvt_Extensions 294 | 295 | # Paket dependency manager 296 | .paket/paket.exe 297 | paket-files/ 298 | 299 | # FAKE - F# Make 300 | .fake/ 301 | 302 | # CodeRush personal settings 303 | .cr/personal 304 | 305 | # Python Tools for Visual Studio (PTVS) 306 | __pycache__/ 307 | *.pyc 308 | 309 | # Cake - Uncomment if you are using it 310 | # tools/** 311 | # !tools/packages.config 312 | 313 | # Tabs Studio 314 | *.tss 315 | 316 | # Telerik's JustMock configuration file 317 | *.jmconfig 318 | 319 | # BizTalk build output 320 | *.btp.cs 321 | *.btm.cs 322 | *.odx.cs 323 | *.xsd.cs 324 | 325 | # OpenCover UI analysis results 326 | OpenCover/ 327 | 328 | # Azure Stream Analytics local run output 329 | ASALocalRun/ 330 | 331 | # MSBuild Binary and Structured Log 332 | *.binlog 333 | 334 | # NVidia Nsight GPU debugger configuration file 335 | *.nvuser 336 | 337 | # MFractors (Xamarin productivity tool) working folder 338 | .mfractor/ 339 | 340 | # Local History for Visual Studio 341 | .localhistory/ 342 | 343 | # BeatPulse healthcheck temp database 344 | healthchecksdb 345 | 346 | # Backup folder for Package Reference Convert tool in Visual Studio 2017 347 | MigrationBackup/ 348 | 349 | # Ionide (cross platform F# VS Code tools) working folder 350 | .ionide/ 351 | -------------------------------------------------------------------------------- /CODE_OF_CONDUCT.md: -------------------------------------------------------------------------------- 1 | # Microsoft Open Source Code of Conduct 2 | 3 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). 4 | 5 | Resources: 6 | 7 | - [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/) 8 | - [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) 9 | - Contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with questions or concerns 10 | -------------------------------------------------------------------------------- /CONTRIBUTING.md: -------------------------------------------------------------------------------- 1 | # Contribute to the Azure DevOps Demo Generator 2 | 3 | Welcome, and thank you for your interest in contributing to the Azure DevOps Demo Generator! 4 | 5 | We welcome participation in a variety of ways, including providing and commenting on issues, issuing pull requests against the code base for new features and fixes, updating and improving documentation, or by contributing templates. This document provides a high-level overview of how you can get involved. 6 | 7 | ## About this project 8 | 9 | Organizations struggle with the number of tasks to adopt a cloud technology due to the lack of an agile methodology to plan, execute, and validate its initial success and deploy into production. 10 | 11 | The purpose of this iniaitive is to simplify the process for organizations by providing DevOps templates for various cloud technologies; you can then use the Azure DevOps Demo Generator to import these into your own DevOps project. The templates include specific Work Items with actionable steps to implement the aforementioned cloud technologies. 12 | 13 | ## Contribution Guidelines 14 | 15 | 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.microsoft.com. 16 | 17 | 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., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA. 18 | 19 | This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or comments. 20 | 21 | # Contributing Templates 22 | 23 | Once you successfully generate and test your template, you can share it with the community: 24 | 25 | Create a pull request to [Azure DevOps Demo Generator](https://github.com/microsoft/azuredevopsgenerator) 26 | 27 | ## Your template must contain the following elements 28 | 29 | We will communicate via email once the template is validated successfully. 30 | 31 | ## Asking Questions 32 | 33 | Have a question? Open an issue using the question template and the `question` label. 34 | 35 | The active community will be eager to assist you. Your well-worded question will serve as a resource to others searching for help. 36 | 37 | ## Providing Feedback 38 | 39 | Your comments and feedback are welcome, and the project team is available via handful of different channels. 40 | 41 | ## Reporting Issues 42 | 43 | To report an issue, select "New Issue" under the [Issues tab] (https://github.com/microsoft/azuredevopsgenerator/issues). 44 | 45 | ### Look For an Existing Issue 46 | 47 | Before you create a new issue, please do a search. 48 | 49 | If you find your issue already exists, make relevant comments and add your [reaction](https://github.com/blog/2119-add-reactions-to-pull-requests-issues-and-comments). Use a reaction in place of a "+1" comment: 50 | 51 | * 👍 - upvote 52 | * 👎 - downvote 53 | 54 | 55 | If you cannot find an existing issue that describes your bug or feature, create a new issue using the guidelines below. 56 | 57 | ### Writing Good Bug Reports and Feature Requests 58 | 59 | File a single issue per problem and feature request. Do not enumerate multiple bugs or feature requests in the same issue. 60 | 61 | 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. 62 | 63 | The more information you can provide, the more likely someone will be successful reproducing the issue and finding a fix. Please use the template for each issue. 64 | 65 | ### Final Checklist 66 | 67 | ## Contributing Fixes 68 | 69 | # Thank You! 70 | 71 | Your contributions to open source, large or small, make great projects like this possible. Thank you for taking the time to contribute. 72 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | MIT License 2 | 3 | Copyright (c) Microsoft Corporation. 4 | 5 | Permission is hereby granted, free of charge, to any person obtaining a copy 6 | of this software and associated documentation files (the "Software"), to deal 7 | in the Software without restriction, including without limitation the rights 8 | to use, copy, modify, merge, publish, distribute, sublicense, and/or sell 9 | copies of the Software, and to permit persons to whom the Software is 10 | furnished to do so, subject to the following conditions: 11 | 12 | The above copyright notice and this permission notice shall be included in all 13 | copies or substantial portions of the Software. 14 | 15 | THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 16 | IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 17 | FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 18 | AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER 19 | LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, 20 | OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE 21 | SOFTWARE 22 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Azure DevOps Generator 2 | 3 | 4 | ## About 5 | 6 | Organizations struggle with the number of tasks to adopt a cloud technology due to the lack of an agile methodology to plan, execute, and validate its initial success and deploy into production. 7 | 8 | The purpose of this iniaitive is to simplify the process for organizations by providing DevOps templates for various cloud technologies; you can then use the Azure DevOps Demo Generator to import these into your own DevOps project. The templates include specific Work Items with actionable steps to implement the aforementioned cloud technologies. 9 | 10 | ## Getting Started 11 | ### Pre-requisites: 12 | 13 | 14 | [Create a DevOps Organizaton](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops#create-an-organization) or use an existing one. 15 | 16 | Process: 17 | 18 | 1. Navigate to the [Azure DevOps Demo Generator](https://azuredevopsdemogenerator.azurewebsites.net/Account/Verify) and sign into your DevOps organization. 19 | 2. Fill in **Project Name**, select your Organization, and select **Choose Template**. 20 | 3. Select **Private** and either upload the appropriate Zip file or link to the raw Github link provided in each folder of this repo. 21 | 4. Select **Create Project** on the main page. 22 | 23 | ## Helpful Links 24 | [Step-by-step instructions on how to get started with the Azure DevOps Demo Generator](https://github.com/microsoft/AzureDevOpsDemoGenerator/blob/master/docs/Using-The-Generator.md) 25 | 26 | ## Contributions 27 | 28 | 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.microsoft.com. 29 | 30 | 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. 31 | For more information on contributing, please visit the [contributor guide](https://github.com/sikovatc/azuredevopsgenerator/blob/master/CONTRIBUTING.md). 32 | -------------------------------------------------------------------------------- /SECURITY.md: -------------------------------------------------------------------------------- 1 | 2 | 3 | ## Security 4 | 5 | Microsoft takes the security of our software products and services seriously, which includes all source code repositories managed through our GitHub organizations, which include [Microsoft](https://github.com/Microsoft), [Azure](https://github.com/Azure), [DotNet](https://github.com/dotnet), [AspNet](https://github.com/aspnet), [Xamarin](https://github.com/xamarin), and [our GitHub organizations](https://opensource.microsoft.com/). 6 | 7 | If you believe you have found a security vulnerability in any Microsoft-owned repository that meets Microsoft's [Microsoft's definition of a security vulnerability](https://docs.microsoft.com/en-us/previous-versions/tn-archive/cc751383(v=technet.10)) of a security vulnerability, please report it to us as described below. 8 | 9 | ## Reporting Security Issues 10 | 11 | **Please do not report security vulnerabilities through public GitHub issues.** 12 | 13 | Instead, please report them to the Microsoft Security Response Center (MSRC) at [https://msrc.microsoft.com/create-report](https://msrc.microsoft.com/create-report). 14 | 15 | If you prefer to submit without logging in, send email to [secure@microsoft.com](mailto:secure@microsoft.com). If possible, encrypt your message with our PGP key; please download it from the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc). 16 | 17 | 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](https://www.microsoft.com/msrc). 18 | 19 | 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: 20 | 21 | * Type of issue (e.g. buffer overflow, SQL injection, cross-site scripting, etc.) 22 | * Full paths of source file(s) related to the manifestation of the issue 23 | * The location of the affected source code (tag/branch/commit or direct URL) 24 | * Any special configuration required to reproduce the issue 25 | * Step-by-step instructions to reproduce the issue 26 | * Proof-of-concept or exploit code (if possible) 27 | * Impact of the issue, including how an attacker might exploit the issue 28 | 29 | This information will help us triage your report more quickly. 30 | 31 | 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](https://microsoft.com/msrc/bounty) page for more details about our active programs. 32 | 33 | ## Preferred Languages 34 | 35 | We prefer all communications to be in English. 36 | 37 | ## Policy 38 | 39 | Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd). 40 | 41 | -------------------------------------------------------------------------------- /WindowsVirtualDesktop/README.MD: -------------------------------------------------------------------------------- 1 | # Azure Windows Virtual Desktop DevOps Generator 2 | 3 | Organizations struggle with the number of tasks to adopt a cloud technology due the lack of an agile methodology to plan, execute, validate its initial success and deploy into production. 4 | 5 | The objective is helping customers to quickly deploy Azure Windows Virtual Desktop following the best practices using Azure DevOps board with agile practices. 6 | 7 | **TODO**Requirements: 8 | 9 | 1. Create or use an existing Azure DevOps organization 10 | 2. [Access to Azure Windows Virtual Desktop DevOps Template](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Forganizations%2Faccounts%2Fcreate-organization%3Fview%3Dazure-devops&data=02%7C01%7Ccrmuno%40microsoft.com%7Cd340cee195414944089708d7e20b9512%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637226411708890912&sdata=sUZ77jIq42KnMWF8%2BCTtEyaoGDDQ1xk9OE1HJGitlaI%3D&reserved=0) 11 | 3. [Access to Azure DevOps Generator](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Fdemo-gen%2Fuse-demo-generator-v2%3Fview%3Dazure-devops&data=02%7C01%7Ccrmuno%40microsoft.com%7Cd340cee195414944089708d7e20b9512%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637226411708900870&sdata=0XTp%2BCwHnScmiiNJly0pv%2ByyFsmU8h6RjXb2V4pdO%2B8%3D&reserved=0) 12 | 13 | 14 | Steps: 15 | 16 | 1. Sign in to Azure DevOps Generator 17 | 18 | 2. Create a new project, ex: “Windows Virtual Desktop” then select your organization “. 19 | 3. Click “Choose template”, select Github. Past the raw url: https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/master/WindowsVirtualDesktop/WindowsVirtualDesktop.zip 20 | 21 | 4. Click “Submit” then “Create Project” 22 | 5. An Azure DevOps project will be created in your organization 23 | 24 | 6. Click on “Backlogs”, you should be able to see “Features” and “User Stories” providing guidance. 25 | This should help your team to discuss, agree on acceptance criteria, delegate ownership, create iterations, track the progress and efficiently deploy Azure Windows Virtual Desktop. 26 | -------------------------------------------------------------------------------- /WindowsVirtualDesktop/WindowsVirtualDesktop.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/WindowsVirtualDesktop/WindowsVirtualDesktop.zip -------------------------------------------------------------------------------- /azuregovernance/AzureGovernance.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/AzureGovernance.zip -------------------------------------------------------------------------------- /azuregovernance/README.MD: -------------------------------------------------------------------------------- 1 | # Azure Governance DevOps Generator 2 | 3 | ## About 4 | 5 | The cloud creates new paradigms for the technologies that support the business. These new paradigms also change how those technologies are adopted, managed, and governed. When entire datacenters can be virtually torn down and rebuilt with one line of code executed by an unattended process, we have to rethink traditional approaches. This is especially true for governance. 6 | 7 | Cloud governance is an iterative process. For organizations with existing policies that govern on-premises IT environments, cloud governance should complement those policies. However, the level of corporate policy integration between on-premises and the cloud varies depending on cloud governance maturity and a digital estate in the cloud. As the cloud estate changes over time, so do cloud governance processes and policies. The following exercises help you understand how start building your initial governance foundation. 8 | 9 | The objective is helping customers to quickly deploy Azure Governance following the best practices using Azure DevOps board with agile practices. 10 | 11 | ## Getting Started 12 | 13 | ### Pre-requisites: 14 | 15 | 1. Create a [DevOps Organization](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops#create-an-organization) or use an existing one. 16 | 17 | 18 | ### Steps 19 | 20 | 1. Go to [http://aka.ms/governance/generator](http://aka.ms/governance/generator), sign into your DevOps organization and you already will be in the correct template selection for Governance. (Please note that if you click on **Choose template**, this template is available under **Cloud Adoption Framework**); 21 | 22 | 2. Fill in **Project Name** and select your Organization. 23 | 24 | 3. Click to **Create Project**. 25 | 26 | 27 | 28 | 4. An Azure DevOps project will be created in your organization. 29 | 30 | 5. In your organization, navigate to the project then click to **Boards**, then on **Backlogs**, you should be able to see **User Stories** and **Tasks** providing guidance on Governance. Bellow is a image with the recommended order to follow: 31 | 32 | 33 | 34 | This should help your team to discuss, agree on acceptance criteria, delegate ownership, create iterations, track the progress and efficiently deploy Azure Governance. 35 | 36 | ## Microsoft Cloud Adoption Framework (CAF) 37 | 38 | Listed in [Tools and Templates](https://docs.microsoft.com/en-us/azure/cloud-adoption-framework/reference/tools-templates#plan) under Plan discipline as a template in the Microsoft Cloud Adoption Framework! 39 | 40 | [Using the Strategy-Plan-Ready-Govern Azure DevOps template](https://azuredevopsdemogenerator.azurewebsites.net/?name=strategyplan) 41 | 42 | 43 | ## Additional information 44 | 45 | If you want just a list with all Governance related links, take a loot at [http://aka.ms/azgovernancelinks](http://aka.ms/azgovernancelinks) 46 | 47 | There are some additional documents that will be useful on your Governance learning and implementation. You can find below: 48 | 49 | * [CAF - Azure Account Organization and Governance](docs/CAF-Azure_Account_Organization_and_Governance.pptx) 50 | * [CAF - Cloud Adoption Framework Overview](docs/CAF-Cloud_Adoption_Framework_Overview.pptx) 51 | * [Cloud Adoption Framework One Pager](docs/Cloud_Adoption_Framework_One_Pager.pdf) 52 | * [CAF - Governance Playbook V2](docs/CAF_Governance_Playbook%20V2.docx) 53 | * [Enterprise Scale Architecture](docs/Enterprise-Scale-Architecture.vsdx) 54 | * [Azure Cloud Architecture Shared Business Unit Model Sample V1](docs/Azure_Cloud_Architecture-Shared-BusinessUnit-Model-Sample_V1.vsdx) 55 | * [Azure Networking Cloud Architecture Sample V1](docs/Azure_Networking_Cloud_Architecture_Sample_v1.vsdx) 56 | * [Azure Management Subscription Architecture Sample V1](docs/Azure_Management-Subscription-Architecture-Sample-v1.vsdx) 57 | * [Governance Implementation Matrix V1](docs/Governance_Implementation_Matrix_v1.xlsx) 58 | 59 | 60 | 61 | 62 | 63 | -------------------------------------------------------------------------------- /azuregovernance/docs/Azure_Cloud_Architecture-Shared-BusinessUnit-Model-Sample_V1.vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Azure_Cloud_Architecture-Shared-BusinessUnit-Model-Sample_V1.vsdx -------------------------------------------------------------------------------- /azuregovernance/docs/Azure_Management-Subscription-Architecture-Sample-v1.vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Azure_Management-Subscription-Architecture-Sample-v1.vsdx -------------------------------------------------------------------------------- /azuregovernance/docs/Azure_Networking_Cloud_Architecture_Sample_v1.vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Azure_Networking_Cloud_Architecture_Sample_v1.vsdx -------------------------------------------------------------------------------- /azuregovernance/docs/CAF-Azure_Account_Organization_and_Governance.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/CAF-Azure_Account_Organization_and_Governance.pptx -------------------------------------------------------------------------------- /azuregovernance/docs/CAF-Cloud_Adoption_Framework_Overview.pptx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/CAF-Cloud_Adoption_Framework_Overview.pptx -------------------------------------------------------------------------------- /azuregovernance/docs/CAF_Governance_Playbook V2.docx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/CAF_Governance_Playbook V2.docx -------------------------------------------------------------------------------- /azuregovernance/docs/Cloud_Adoption_Framework_One_Pager.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Cloud_Adoption_Framework_One_Pager.pdf -------------------------------------------------------------------------------- /azuregovernance/docs/Enterprise-Scale-Architecture.vsdx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Enterprise-Scale-Architecture.vsdx -------------------------------------------------------------------------------- /azuregovernance/docs/Governance_Implementation_Matrix_v1.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/Governance_Implementation_Matrix_v1.xlsx -------------------------------------------------------------------------------- /azuregovernance/docs/ps-cli-scripts/RG-Tag-Template.cli: -------------------------------------------------------------------------------- 1 | # ------------------- CLI -------------------------------- 2 | # CLI Deploy resource group with tags 3 | 4 | # Login 5 | az login 6 | az login --tenant 'The value of this argument can either be an .onmicrosoft.com domain or the Azure object ID for the tenant' 7 | 8 | # TODO: Set Variables... 9 | $resourceGroup = 'rgCliRgTemplate' 10 | $resoureGroupLocation = 'eastus' 11 | 12 | # Create RG and tags... 13 | az group create --name $resourceGroup --location $resoureGroupLocation 14 | 15 | # TODO: Fill in tag values... 16 | az group update -n $resourceGroup --tags 'ApplicationName=Application Name' 'Approver=Email' 'BudgetAmount=$' 'BusinessUnit=FINANCE, MARKETING, Product Name, CORP, SHARED' 'CostCenter=Number' 'DR=Mission-critical, Critical, Essential' 'EndDate=Date' 'Env=Prod, Dev, QA, Stage, Test' 'Owner=Email' 'Requestor=Email' 'ServiceClass=Dev, Bronze, Silver, Gold' 'StartDate=Date' 17 | 18 | # Create and set lock (optional)... 19 | az group lock create --lock-type CanNotDelete -n DoNotDelete -g $resourceGroup -------------------------------------------------------------------------------- /azuregovernance/docs/ps-cli-scripts/RG-Tag-Template.ps1: -------------------------------------------------------------------------------- 1 | # ------------------- PowerShell ----------------------------------- 2 | # PS Deploy resource group with tags 3 | 4 | # Login & Subscription selection 5 | Login-AzureRmAccount 6 | 7 | # TODO: Enter the variables... 8 | $resourceGroupName = "rgPsRgTemplate" 9 | $location = "eastus" 10 | $subscriptionId = "87fb4835-b4c1-4119-93b6-5c2d91ce07c1" 11 | 12 | # Subscription... 13 | Select-AzureRmSubscription -SubscriptionId $subscriptionId 14 | Get-AzureRmSubscription -SubscriptionId $subscriptionId | Set-AzureRmContext 15 | 16 | # Set the tags... 17 | # TODO: Fill in tag values... 18 | $tags = @{"ApplicationName"="Application Name"; "Approver"="Email"; "BudgetAmount"="$"; "BusinessUnit"="FINANCE, MARKETING, Product Name, CORP, SHARED"; "CostCenter"="Number"; "DR"="Mission-critical, Critical, Essential"; "EndDate"="Date"; "Env"="Prod, Dev, QA, Stage, Test"; "Owner"="Email"; "Requestor"="Email"; "ServiceClass"="Dev, Bronze, Silver, Gold"; "StartDate"="Date"} 19 | 20 | #Create the RG and set tags... 21 | New-AzureRmResourceGroup -Name $resourceGroupName -Location $location -Tag $tags 22 | 23 | # Create and set lock (optional)... 24 | $scope = "/subscriptions/" + $subscriptionId + "/resourceGroups/" + $resourceGroupName 25 | New-AzureRmResourceLock -LockLevel "CanNotDelete" -LockName "DoNotDelete" -Scope $scope -Force 26 | 27 | 28 | -------------------------------------------------------------------------------- /azuregovernance/docs/ps-cli-scripts/RG-Tag-Template.txt: -------------------------------------------------------------------------------- 1 | # ------------------- PowerShell ----------------------------------- 2 | # PS Deploy resource group with tags 3 | 4 | # Login & Subscription selection 5 | Login-AzureRmAccount 6 | 7 | # TODO: Enter the variables... 8 | $resourceGroupName = "rgPsRgTemplate" 9 | $location = "eastus" 10 | $subscriptionId = "87fb4835-b4c1-4119-93b6-5c2d91ce07c1" 11 | 12 | # Subscription... 13 | Select-AzureRmSubscription -SubscriptionId $subscriptionId 14 | Get-AzureRmSubscription -SubscriptionId $subscriptionId | Set-AzureRmContext 15 | 16 | # Set the tags... 17 | # TODO: Fill in tag values... 18 | $tags = @{"ApplicationName"="Application Name"; "Approver"="Email"; "BudgetAmount"="$"; "BusinessUnit"="FINANCE, MARKETING, Product Name, CORP, SHARED"; "CostCenter"="Number"; "DR"="Mission-critical, Critical, Essential"; "EndDate"="Date"; "Env"="Prod, Dev, QA, Stage, Test"; "Owner"="Email"; "Requestor"="Email"; "ServiceClass"="Dev, Bronze, Silver, Gold"; "StartDate"="Date"} 19 | 20 | #Create the RG and set tags... 21 | New-AzureRmResourceGroup -Name $resourceGroupName -Location $location -Tag $tags 22 | 23 | # Create and set lock (optional)... 24 | $scope = "/subscriptions/" + $subscriptionId + "/resourceGroups/" + $resourceGroupName 25 | New-AzureRmResourceLock -LockLevel "CanNotDelete" -LockName "DoNotDelete" -Scope $scope -Force 26 | 27 | 28 | -------------------------------------------------------------------------------- /azuregovernance/docs/ps-cli-scripts/RG-Tag-Template.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/docs/ps-cli-scripts/RG-Tag-Template.zip -------------------------------------------------------------------------------- /azuregovernance/docs/ps-cli-scripts/a: -------------------------------------------------------------------------------- 1 | 2 | -------------------------------------------------------------------------------- /azuregovernance/pictures/azcommunity.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/pictures/azcommunity.png -------------------------------------------------------------------------------- /azuregovernance/pictures/caf.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/pictures/caf.png -------------------------------------------------------------------------------- /azuregovernance/pictures/createproject.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/pictures/createproject.png -------------------------------------------------------------------------------- /azuregovernance/pictures/governance.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuregovernance/pictures/governance.png -------------------------------------------------------------------------------- /azuresentinel/AzureSentinelDevopsBoardTemplate.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/azuresentinel/AzureSentinelDevopsBoardTemplate.zip -------------------------------------------------------------------------------- /azuresentinel/README.MD: -------------------------------------------------------------------------------- 1 | # Azure Sentinel DevOps Generator 2 | 3 | Organizations struggle with the number of tasks to adopt a cloud technology due the lack of an agile methodology to plan, execute, validate its initial success and deploy into production. 4 | Adopting a cloud native SIEM 5 | 6 | The objective is helping customers to quickly deploy Azure Sentinel following the best practices using Azure DevOps board with agile practices. 7 | 8 | **TODO**Requirements: 9 | 10 | 1. Create or use an existing Azure DevOps organization 11 | 2. [Access to Azure Sentinel DevOps Template](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Forganizations%2Faccounts%2Fcreate-organization%3Fview%3Dazure-devops&data=02%7C01%7Ccrmuno%40microsoft.com%7Cd340cee195414944089708d7e20b9512%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637226411708890912&sdata=sUZ77jIq42KnMWF8%2BCTtEyaoGDDQ1xk9OE1HJGitlaI%3D&reserved=0) 12 | 3. [Access to Azure DevOps Generator](https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fazure%2Fdevops%2Fdemo-gen%2Fuse-demo-generator-v2%3Fview%3Dazure-devops&data=02%7C01%7Ccrmuno%40microsoft.com%7Cd340cee195414944089708d7e20b9512%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637226411708900870&sdata=0XTp%2BCwHnScmiiNJly0pv%2ByyFsmU8h6RjXb2V4pdO%2B8%3D&reserved=0) 13 | 14 | 15 | Steps: 16 | 17 | 1. Sign in to Azure DevOps Generator 18 | 19 | 2. Create a new project, ex: “Azure Sentinel POC” then select your organization “. 20 | 3. Click “Choose template”, select Github. Past the raw url: https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/master/azuresentinel/AzureSentinel.zip 21 | 22 | 4. Click “Submit” then “Create Project” 23 | 5. An Azure DevOps project will be created in your organization 24 | 25 | 6. Click on “Backlogs”, you should be able to see “Features” and “User Stories” providing guidance. 26 | This should help your team to discuss, agree on acceptance criteria, delegate ownership, create iterations, track the progress and efficiently deploy Azure Sentinel. 27 | -------------------------------------------------------------------------------- /caf.png: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/caf.png -------------------------------------------------------------------------------- /nist800171Rev2/Customer Reponsiblity Matrix - NIST 800-171.xlsx: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/nist800171Rev2/Customer Reponsiblity Matrix - NIST 800-171.xlsx -------------------------------------------------------------------------------- /nist800171Rev2/NIST 800-171 Compliance as a Service.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/nist800171Rev2/NIST 800-171 Compliance as a Service.pdf -------------------------------------------------------------------------------- /nist800171Rev2/NIST800171Rev2.zip: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/563776c51c9e4a4cdeaaa664f683d57d796c54fa/nist800171Rev2/NIST800171Rev2.zip -------------------------------------------------------------------------------- /nist800171Rev2/README.MD: -------------------------------------------------------------------------------- 1 | # Azure NIST 800-171 Rev2 DevOps Template 2 | 3 | ## About 4 | 5 | Implementing NIST 800-171 compliance across your Azure environments involves a set of customer responsibilities as well as actions taken by the cloud provider. Please refer to the included **Customer Responsibility Matrix** for greater detail on those responsibilities. 6 | 7 | By importing the NIST 800-171 DevOps template, you will be able to complete actionable Work Items that correspond to customer responsibiities in order to implement compliance. 8 | 9 | ## Getting Started 10 | 11 | Pre-requisites: 12 | [Create a DevOps Organizaton](https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops#create-an-organization) or use an existing one. 13 | 14 | Process: 15 | 16 | 1. Navigate to the [Azure DevOps Generator](https://azuredevopsdemogenerator.azurewebsites.net/) and sign into your DevOps organization. 17 | 2. Fill in **Project Name**, select your Organization, and select **Choose Template**. 18 | 3. Select Private and either upload the Zip file download in this branch or link to the [NIST 800-171 Template Github Raw URL](https://raw.githubusercontent.com/microsoft/azuredevopsgenerator/master/nist800171Rev2/NIST800171Rev2.zip). 19 | 4. Select **Create Project** on the main page. 20 | 21 | ## Helpful Links 22 | 23 | [NIST 800-171 Official Documentation](https://csrc.nist.gov/publications/detail/sp/800-171/rev-2/final) 24 | 25 | [Microsoft and NIST 800-171](https://docs.microsoft.com/en-us/microsoft-365/compliance/offering-nist-sp-800-171?view=o365-worldwide) 26 | 27 | 28 | --------------------------------------------------------------------------------