updated root files

Author: dougeby

.acrolinx-config.edn

@@ -0,0 +1,2 @@
+{:allowed-branchname-matches ["master" "release-.*" "sandbox-.*"]
+ :allowed-filename-matches ["intune-azure" "intune-classic" "intune-user-help" "intune"]}

.gitignore

@@ -1,8 +1,18 @@
 log/
+xhtml/
+packages/
 obj/
 _site/
+Tools/NuGet/
 .optemp/
-_themes*/
-_repo.*/
+_themes/
 
-.openpublishing.buildcore.ps1
+
+# Visual Studio and VS Code files
+.vscode/*
+
+
+
+.openpublishing.build.mdproj
+.openpublishing.buildcore.ps1
+packages.config

CODE_OF_CONDUCT.md

@@ -0,0 +1,9 @@
+# Microsoft Open Source Code of Conduct
+
+This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/).
+
+Resources:
+
+- [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/)
+- [Microsoft Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/)
+- Contact [[email protected]](mailto:[email protected]) with questions or concerns

LICENSE

@@ -1,4 +1,4 @@
-Attribution 4.0 International
+Attribution 4.0 International
 
 =======================================================================
 
@@ -33,7 +33,7 @@ exhaustive, and do not form part of our licenses.
      material not subject to the license. This includes other CC-
      licensed material, or material used under an exception or
      limitation to copyright. More considerations for licensors:
-	wiki.creativecommons.org/Considerations_for_licensors
+     wiki.creativecommons.org/Considerations_for_licensors
 
      Considerations for the public: By using one of our public
      licenses, a licensor grants the public permission to use the
@@ -50,7 +50,7 @@ exhaustive, and do not form part of our licenses.
      Although not required by our licenses, you are encouraged to
      respect those requests where reasonable. More_considerations
      for the public: 
-	wiki.creativecommons.org/Considerations_for_licensees
+     wiki.creativecommons.org/Considerations_for_licensees
 
 =======================================================================
 

README.md

@@ -1,3 +1,50 @@
 ## Microsoft Open Source Code of Conduct
+
 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 [[email protected]](mailto:[email protected]) with any additional questions or comments.
+For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) or contact [[email protected]](mailto:[email protected]) with any additional questions or comments.
+
+# Docs.microsoft.com Github repository
+
+You've found one of the GitHub repositories that houses the source for content published to [https://docs.microsoft.com](https://docs.microsoft.com/.), home of all technical content for Microsoft's Cloud and Enterprise Division.
+
+## Contribute to your documentation
+We **want and encourage contributions** from our community (users, customers, partners, friends on other planets) and Microsoft employees to improve your documentation. Here are some tips:
+
+* **Create a GitHub account**: Sign up is free at [GitHub.com](https://www.github.com).
+
+* **Use your browser**: There are two options: 
+
+    **Option 1: Edit directly from docs.microsoft.com**  
+    1. Go to the topic, such as [https://docs.microsoft.com/mem/intune/protect/troubleshoot-policies-in-microsoft-intune](mem/intune/protect/troubleshoot-policies-in-microsoft-intune.md). 
+    2. Select **Edit** (top right). This shows the markdown file in the GitHub repository.
+    3. Select the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip. 
+    4. Make your changes, and then **commit** your changes. 
+    5. Create the pull request.
+    
+    **Option 2: Find the article in this repository, and update**  
+    1. Most topics are in `https://github.com/MicrosoftDocs/memdocs/tree/master/memdocs/intune`. In this folder, search for the topic name, such as `troubleshoot-policies-in-microsoft-intune`. 
+    2. Select the link, and click the pencil icon. When you hover over the pencil icon, you'll see the **Edit this file** tooltip. 
+    3. Make your changes, and then **commit** your changes. 
+    4. Create the pull request. 
+
+  When you make an update, you may be prompted to sign a license agreement. This is a one-time task. So any future updates by your GitHub username won't need to sign again. 
+  
+  The value in the `author` metadata (at the top of every topic) lists the GitHub author. In the `troubleshoot-policies-in-microsoft-intune` example, you'll see `MandiOhlinger`. In your pull request, you can also mention (@*authorValue*) the author if you like.
+  
+* **MSFT Employees**: After you create a GitHub account, link it to your Microsoft email address. When your account is linked, you don't have to sign a license agreement to make an update. Steps:
+
+  1. On a device with corpnet, go to [GitHub account setup](https://review.docs.microsoft.com/en-us/help/contribute/contribute-get-started-setup-github?branch=master). If you're not on corpnet, this link returns a 404.
+  
+    Creating a GitHub account, and linking to your Microsoft account is a one-time thing. When your account is linked, you don't have to sign a license agreement to make an update. 
+
+  2. In your browser, go to the article, and select **Edit**. Switch to the private repo (IntuneDocs-pr):  
+    **From**: https://github.com/MicrosoftDocs/memdocs/...  
+    **To**: https://github.com/MicrosoftDocs/memdocs-pr/...
+  
+  3. Select the pencil icon, and make your changes. 
+
+## Use markdown to format your topic
+All the articles in this repository use GitHub-flavored markdown. Here's a list of resources to get started:
+
+* [Markdown basics](https://help.github.com/articles/basic-writing-and-formatting-syntax/)
+* [Printable markdown cheatsheet](https://guides.github.com/pdfs/markdown-cheatsheet-online.pdf)

SECURITY.md

@@ -0,0 +1,41 @@
+<!-- BEGIN MICROSOFT SECURITY.MD V0.0.3 BLOCK -->
+
+## Security
+
+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/).
+
+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.
+
+## Reporting Security Issues
+
+**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](https://msrc.microsoft.com/create-report).
+
+If you prefer to submit without logging in, send email to [[email protected]](mailto:[email protected]).  If possible, encrypt your message with our PGP key; please download it from the the [Microsoft Security Response Center PGP Key page](https://www.microsoft.com/en-us/msrc/pgp-key-msrc).
+
+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).
+
+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](https://microsoft.com/msrc/bounty) page for more details about our active programs.
+
+## Preferred Languages
+
+We prefer all communications to be in English.
+
+## Policy
+
+Microsoft follows the principle of [Coordinated Vulnerability Disclosure](https://www.microsoft.com/en-us/msrc/cvd).
+
+<!-- END MICROSOFT SECURITY.MD BLOCK -->

samplefile1.md

@@ -0,0 +1,44 @@
+# required metadata
+
+title: [ARTICLE TITLE | SERVICE NAME]
+description:
+keywords:
+author: [GITHUB USERNAME]
+manager: [ALIAS]
+ms.date: 04/28/2016
+ms.topic: article
+ms.prod:
+ms.service:
+ms.technology:
+ms.assetid: [GET ONE FROM guidgenerator.com]
+
+# optional metadata
+
+#ROBOTS:
+#audience:
+#ms.devlang:
+#ms.reviewer: [ALIAS]
+#ms.suite: ems
+#ms.tgt_pltfrm:
+#ms.custom:
+
+---
+Lorem ipsum dolor sit amet, consectetur adipiscing elit. Phasellus laoreet volutpat aliquet. Suspendisse venenatis ex vitae fringilla suscipit. Maecenas eu nibh vitae lorem porta mollis. Nam in nisi eu nisi hendrerit pretium. Nullam vel gravida felis. Pellentesque luctus massa mi. Proin ultricies egestas erat. Morbi ut tincidunt nulla, eu ornare urna. Fusce sit amet aliquam est, at efficitur erat. Curabitur blandit mauris in dolor luctus feugiat. Proin sit amet dignissim arcu. Proin turpis lorem, congue ut bibendum non, posuere in eros. Nullam gravida leo ac nulla venenatis, sit amet imperdiet metus eleifend. Nullam id pharetra elit.
+
+Aenean porta sit amet nisl quis posuere. In ut magna felis. Nulla quis euismod odio. Sed scelerisque nisi justo, sed egestas odio volutpat non. Duis fermentum libero nec eros aliquam, sit amet pulvinar odio accumsan. Sed scelerisque felis tristique arcu euismod lobortis. Nunc id volutpat lectus. In pharetra sapien a ullamcorper gravida. Sed ultricies tellus nec magna posuere tempus.
+
+Etiam ac mauris in odio tincidunt tempor. Mauris vel orci dictum enim egestas sagittis sed eu mi. Nulla augue urna, tincidunt eu enim nec, scelerisque suscipit eros. Aliquam imperdiet diam sit amet dictum semper. Sed tincidunt diam id erat scelerisque, in sagittis nibh tempus. Ut pharetra leo vitae fringilla faucibus. Aliquam sem nisi, mattis eget sollicitudin non, suscipit quis magna. Vestibulum pulvinar auctor finibus. Praesent at sollicitudin elit, sed blandit diam. Cras non viverra velit, eu mattis ipsum. Fusce sed laoreet libero, vitae cursus nisl. Ut semper est eget felis lobortis tempus faucibus vitae libero. Sed lacus tellus, sagittis non vehicula vitae, ornare nec lacus.
+
+Proin metus mi, ullamcorper eu mollis eget, pulvinar ut enim. Ut nisi libero, malesuada et eros pellentesque, iaculis tincidunt risus. Nulla ut tincidunt nunc. Integer et rutrum nunc, a accumsan ante. Fusce nec neque sem. Phasellus quis purus et dui pharetra tempor nec pharetra erat. Integer vel quam quis nulla vestibulum maximus vitae vel nisi. In vitae rhoncus nibh. Ut at euismod erat. Phasellus a cursus ante. Fusce quis auctor erat.
+
+In cursus finibus metus vel bibendum. Mauris congue maximus metus vitae ultrices. Aenean tincidunt sapien id quam congue, eget pharetra velit mollis. Aenean eleifend ante sed nulla tempor, ut ullamcorper ante pulvinar. Proin ultricies mauris ut mi auctor rhoncus. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam porttitor velit tortor, nec sagittis eros consectetur at. Etiam sit amet ultrices metus, non sagittis elit. Donec et dolor in nisl vehicula rutrum eu vel tellus.
+
+Cras vitae diam ac dui luctus tempus. Cras in eros vitae neque pretium consequat. Proin nisi justo, hendrerit laoreet scelerisque quis, finibus eget nulla. Sed a laoreet erat, ac molestie quam. Suspendisse et viverra nisi. Vivamus convallis interdum faucibus. Donec viverra ante sit amet massa consectetur blandit. Morbi id dolor enim. Aliquam sit amet mattis velit, sit amet rhoncus purus. Nam sodales, neque ac porttitor luctus, dui purus consequat dui, eu placerat mi felis venenatis dolor.
+
+Suspendisse potenti. Morbi vel cursus lacus, nec aliquam leo. Curabitur tempus porta aliquet. Mauris a ipsum nec justo tristique porta. In quis sodales ligula, ut tincidunt urna. Vivamus a ligula hendrerit, dictum sapien sit amet, molestie nisi. Donec quis ante vitae ligula mattis tincidunt. Praesent pharetra nisi ligula, quis scelerisque dui auctor at. Nam id iaculis ipsum. Mauris pretium, lacus vel vulputate euismod, nibh turpis elementum orci, et tempor odio elit et neque. Aenean dignissim interdum rutrum. Pellentesque feugiat volutpat neque vel dictum. Phasellus id convallis nisi. Quisque turpis sapien, pulvinar ut tortor a, gravida gravida arcu. Sed tempor malesuada odio ut ornare. Aenean a urna libero.
+
+Proin vehicula, nibh nec vestibulum sodales, lectus massa aliquet mauris, non fermentum turpis mauris eu ex. Fusce condimentum aliquam velit. Vivamus sit amet ante a magna tristique dignissim et in libero. Nulla sit amet sagittis diam. Vivamus sagittis mattis tincidunt. Phasellus convallis luctus purus, sit amet mattis urna tempor ut. Etiam lacinia eleifend risus sollicitudin euismod. Etiam non gravida ante. Mauris non justo ut elit laoreet volutpat ut eget velit. Donec sit amet bibendum mauris. Mauris quis odio ut mauris pellentesque blandit vel eget massa. Duis in venenatis tellus. Pellentesque quis sem nisi. Proin ut quam tristique, pharetra turpis ut, lacinia nisi.
+
+Morbi dictum vel magna ac dictum. Proin ultricies gravida est, quis pulvinar erat accumsan ac. Aliquam euismod et mauris in semper. Class aptent taciti sociosqu ad litora torquent per conubia nostra, per inceptos himenaeos. Nullam gravida semper mauris sollicitudin malesuada. Duis vitae placerat nisl. Sed luctus massa id dolor ultricies blandit. Mauris posuere congue auctor. Donec tincidunt lectus sit amet interdum convallis. Donec efficitur elit a lorem vulputate sollicitudin. Vestibulum sit amet elit sed ipsum mollis euismod mollis vel lectus. Donec bibendum nulla libero, eget fringilla arcu aliquet vel.
+
+Aliquam erat volutpat. Donec sed lacinia lorem. Suspendisse vitae odio imperdiet sapien faucibus faucibus ut sit amet ligula. Maecenas fermentum non magna eu rutrum. Curabitur auctor urna sit amet imperdiet porttitor. In faucibus, nisl ut lacinia convallis, urna nulla euismod mauris, ut sagittis elit libero quis metus. Integer semper risus ac mattis hendrerit.