<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Application-Guard on Anything About IT</title><link>https://www.verboon.info/tags/application-guard/</link><description>Recent content in Application-Guard on Anything About IT</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 21 Nov 2020 17:24:13 +0000</lastBuildDate><atom:link href="https://www.verboon.info/tags/application-guard/index.xml" rel="self" type="application/rss+xml"/><item><title>Preparing my Application Guard for Office test lab</title><link>https://www.verboon.info/2020/11/preparing-my-application-guard-for-office-test-lab/</link><pubDate>Sat, 21 Nov 2020 17:24:13 +0000</pubDate><guid>https://www.verboon.info/2020/11/preparing-my-application-guard-for-office-test-lab/</guid><description>&lt;p&gt;Hello everyone, today I wanted to see application guard for office in action. If you are not familiar with application guard for office, I suggest you read the following articles / documentation.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#"&gt;Microsoft Defender Application Guard for Office&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#"&gt;Application Guard for Office&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And now let me walk you through the steps to get application guard for office working in your test lab.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Deploy Windows 10 20H1 or 20H2&lt;/li&gt;
&lt;li&gt;When running your test client in Hyper-V you have to enable &lt;a href="#"&gt;nested virtualization&lt;/a&gt; so that we can later enable Application Guard
 &lt;img src="images/112120_1710_Preparingmy1.png" alt=""&gt;

&lt;/li&gt;
&lt;li&gt;Next, we turn on the Microsoft Defender Application Guard. Now if your system does not meet the minimum &lt;a href="#"&gt;requirements&lt;/a&gt; the option is greyed out as shown in the screenshot below.

 &lt;img src="images/112120_1710_Preparingmy2.png" alt=""&gt;


But luckily there is a workaround described &lt;a href="#"&gt;here&lt;/a&gt;. Once you have added these registry keys, you will be able to enable Application Guard

 &lt;img src="images/112120_1710_Preparingmy3.png" alt=""&gt;

&lt;/li&gt;
&lt;li&gt;Now we have to enable Microsoft Defender Application Guard in managed mode, so that it can be used for Microsoft Edge and Office. Open the Group Policy editor and navigate to: Computer Configuration \ Administrative templates \ Windows Components \ Microsoft Defender Application Guard and open the setting: Turn on Microsoft Defender Application Guard in Managed Mode and set the value to 3 If you want to enable Application Guard for Edge and Office or 2 for Office only.

 &lt;img src="images/112120_1710_Preparingmy4.png" alt=""&gt;

&lt;/li&gt;
&lt;li&gt;Now that we have Defender Application Guard ready, let us move on to Office. The &lt;a href="#"&gt;official documentation&lt;/a&gt; mentions Office Beta Channel Build version 2008 16.0.13212 or later, however as per &lt;a href="#"&gt;this announcement&lt;/a&gt; it should work with the Insider current channel as well. Configure the following group policy settings for Office 365 Apps for Enterprise to enable insider releases:User Configuration \ Administrative Templates \ Microsoft Office 2016 \ miscellaneous \ Show the option for Office Insider&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
 &lt;img src="images/112120_1710_Preparingmy5.png" alt=""&gt;

&lt;/p&gt;</description></item></channel></rss>