EelcoLabordus\/ARM-Repo (github.com)<\/a><\/p>\n\n\n\n This blog is part of a series of blog about “Building an ARM Repository.”<\/a><\/p>\n\n\n\n The directory needs to contain the following files to publish a ARM template into the Azure Template Spec.<\/p>\n\n\n\n This is the actual ARM file itself, this contains the ARM code that needs to be executed.<\/p>\n\n\n\n For more information about the creation of a ARMTTK <\/a>request read the following: Checking ARM files for ARM-TTK<\/a><\/p>\n\n\n\n First run the build one time to see what checks it feels, fix and\/or copy those checks from the result logs of the build run.<\/p>\n\n\n\n For more information about the creation of a AzSK <\/a>request read the following: Checking ARM files for Security<\/a><\/p>\n\n\n\n First run the build one time to see what checks it feels, fix and\/or copy those checks from the result logs of the build run.<\/p>\n\n\n\n This file contains all the information needed for publishing the ARM template in Azure Template Specs. What is the name of the template, the description and the Display name.<\/p>\n\n\n\n Before you can make an exclusion for the ARM checks you first need to run the build once. After the build is done it will fail on the ARM check part.<\/p>\n\n\n\n When you select the job that has failed you have on the right side three dots. Select them and select \u201cDownload Logs\u201d. Download the zip file and extract the file.<\/p>\n\n\n\n After downloading the job logs you can extract them and open the files where the test are stored. You can use this information to improve (Preferred) your script or create exclusions for your script.<\/p>\n","protected":false},"excerpt":{"rendered":" Azure DevOps Repository Everything starts with the Repository that is located with Azure DevOps site:\u00a0ARM-Repo. After cloning the repository, you<\/p>\nLayout of the directory<\/h2>\n\n\n\n
[Name].json<\/strong><\/h4>\n\n\n\n
[Name].ARMTTKSkipControls.csv<\/strong><\/h4>\n\n\n\n
apiVersions-Should-Be-Recent\nDeploymentTemplate-Must-Not-Contain-Hardcoded-Uri\nLocation-Should-Not-Be-Hardcoded\nSecure-String-Parameters-Cannot-Have-Default\n<\/pre>\n\n\n\n
TIP<\/h5>\n\n\n\n
[Name].AzSSkipControlsFromFile.csv<\/strong><\/h4>\n\n\n\n
\"ControlId\",\"FeatureName\",\"Status\",\"SupportedResources\",\"Severity\",\"PropertyPath\",\"LineNumber\",\"CurrentValue\",\"ExpectedProperty\",\"ExpectedValue\",\"ResourcePath\",\"ResourceLineNumber\",\"Description\",\"FilePath\"\n\"Azure_VNet_NetSec_Justify_IPForwarding_for_NICs\",\"VirtualNetworkInterface\",\"Failed\",\"Microsoft.Network\/networkInterfaces\",\"High\",\"Not found\",\"-1\",\"\",\"$.properties.enableIPForwarding\",\"'False'\",\"resources[0]\",\"236\",\"Use of IP Forwarding on any NIC in a virtual network should be scrutinized\",\".\\ActiveDirectoryServerDeploy.json\"\n\"Azure_VNet_NetSec_Configure_NSG\",\"VirtualNetworkInterface\",\"Failed\",\"Microsoft.Network\/networkInterfaces\",\"Medium\",\"Not found\",\"-1\",\"\",\"$.properties.networkSecurityGroup.id\",\"Non-null string\",\"resources[0]\",\"236\",\"NSG should be used for subnets in a virtual network to permit traffic only on required inbound\/outbound ports. NSGs should not have a rule to allow any-to-any traffic\",\".\\ActiveDirectoryServerDeploy.json\"\n<\/pre>\n\n\n\n
TIP<\/h5>\n\n\n\n
[Name].metadata.json<\/strong><\/h4>\n\n\n\n
{\n \"$schema\": \"https:\/\/aka.ms\/azure-quickstart-templates-metadata-schema#\",\n \"itemDisplayName\": \"HIP_Active_Directory_Domain_Services\",\n \"type\": \"QuickStart\",\n \"description\": \"This VmRole will allow you to deploy an 2012R2, 2016 or 2019 Domain Controller server in one of the following scenarios: 1.Create a new forest, 2. Create a new child domain at an existing forest, 3. Add a DC to an existing domain. Only the first two scenarios will setup a new AD domain and prepopulated it with default AD objects. More detailed information (only accessible from Externbeheer) of this role can be found at: SMS Sharepoint \/ Architecture \/ Hybrid Datacenter \/ Active Directory Domain Services \/ Active Directory Domain Services - Technical Design.docx. DSC will be used for final configuration. The following features are installed: 'AD-Domain-Services','DNS','GPMC','RSAT-File-Services'. OS: Windows 2012R2, Windows 2016 and Windows 2019 compatible.\",\n \"summary\": \"HIP_Active_Directory_Domain_Services\",\n \"githubUsername\": \"EelcoLabordus\",\n \"dateUpdated\": \"09-02-2020\"\n }\n<\/pre>\n\n\n\nARM validation Reports<\/h2>\n\n\n\n
![\"\"](\"http:\/\/192.168.100.7\/wp-content\/uploads\/2021\/05\/failed-job.png\")
<\/figure>\n\n\n\n![\"\"](\"http:\/\/192.168.100.7\/wp-content\/uploads\/2021\/05\/download-job.png\")
<\/figure>\n\n\n\n