<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>News on Ru Campbell MVP</title>
    <link>https://campbell.scot/categories/news/</link>
    <description>Recent content in News on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sat, 30 Jan 2021 22:13:50 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/categories/news/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Understanding Application Guard for Office, Now Generally Available</title>
      <link>https://campbell.scot/understanding-application-guard-for-office-now-generally-available/</link>
      <pubDate>Sat, 30 Jan 2021 22:13:50 +0000</pubDate>
      <guid>https://campbell.scot/understanding-application-guard-for-office-now-generally-available/</guid>
      <description>&lt;p&gt;&lt;strong&gt;Application Guard&lt;/strong&gt; first appeared in Windows 10 1709 (&amp;ldquo;Fall Creators Update&amp;rdquo;) to isolate Edge browser activity within a Hyper V container.  Microsoft now extends that same idea to Word, Excel, and PowerPoint in Office 365 ProPlus Microsoft 365 Apps for Enterprise on Windows 10&amp;hellip;&lt;/p&gt;
&lt;p&gt;&amp;hellip; if you have Microsoft 365 E5 or E5 Security.  You knew that was coming!&lt;/p&gt;
&lt;p&gt;With &lt;strong&gt;Application Guard for Office&lt;/strong&gt;, your files can open in a sandbox without access local or network storage.  This provides an additional layer of protection against threats such as ransomware, for which Office apps are infamous as an attack surface.  There&amp;rsquo;s a significant catch: a standard configuration of Application Guard &lt;em&gt;will&lt;/em&gt; allow users to bypass it if they say they trust the file, therefore executing it in the normal way; resource access included.  You can change this default behaviour though, so keep reading.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft 365 Updates from Build 2020</title>
      <link>https://campbell.scot/microsoft-365-updates-from-build-2020/</link>
      <pubDate>Thu, 21 May 2020 17:55:43 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-365-updates-from-build-2020/</guid>
      <description>&lt;p&gt;Build 2020 had some nice bits of M365 related news.  Microsoft deserves commendation for sticking to the schedule and pulling this off (remotely) during the COVID-19 lockdown - Apple has delayed WWDC and Google just gave up on I/O.  I&amp;rsquo;ve summarised (bullet points!) my favourite updates below.  I will update it I find I&amp;rsquo;ve missed something good.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Azure AD&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&#34;https://aka.ms/publisherverification&#34;&gt;Publisher Verification&lt;/a&gt; lets developers verified through the Microsoft Partner Center stick a verified badge on their AAD apps.  There is a new setting in &lt;strong&gt;AAD&lt;/strong&gt; &amp;gt; &lt;strong&gt;Consent and permissions&lt;/strong&gt; to &lt;strong&gt;Allow for apps from this organisation and verified publishers&lt;/strong&gt;, which is Microsoft&amp;rsquo;s recommendation (as opposed to allowing user consent for all/none).&lt;/li&gt;
&lt;li&gt;&lt;a href=&#34;https://azure.microsoft.com/en-us/services/active-directory/external-identities/&#34;&gt;External Identities&lt;/a&gt; is now in public preview.  This allows invited external users to &amp;lsquo;bring their own identity&amp;rsquo; (BYOI) and sign in with a federated service like Google, Facebook, or another SAML2/WS-Fed IdP.&lt;/li&gt;
&lt;li&gt;Microsoft Authentication Libraries (MSAL) &lt;a href=&#34;https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-v2-angular&#34;&gt;now support Angular&lt;/a&gt; and the &lt;a href=&#34;https://github.com/AzureAD/microsoft-identity-web/wiki&#34;&gt;ASP.NET web libraries are in public preview&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Development&lt;/strong&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
