<?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>Information-Protection on Ru Campbell MVP</title>
    <link>https://campbell.scot/tags/information-protection/</link>
    <description>Recent content in Information-Protection on Ru Campbell MVP</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 13 Jun 2021 17:38:11 +0000</lastBuildDate>
    <atom:link href="https://campbell.scot/tags/information-protection/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Three Cool Things To Do With Azure Information Protection</title>
      <link>https://campbell.scot/three-cool-things-to-do-with-azure-information-protection/</link>
      <pubDate>Sun, 13 Jun 2021 17:38:11 +0000</pubDate>
      <guid>https://campbell.scot/three-cool-things-to-do-with-azure-information-protection/</guid>
      <description>&lt;p&gt;In my last blog, I wrote about &lt;a href=&#34;https://campbell.scot/3-considerations-for-aip-deployments/&#34;&gt;three considerations for your Azure Information Protection deployments&lt;/a&gt; and commented on often overlooked potential downsides, or at least areas with which to be cautious. In hindsight, it all feels a bit negative.  I am, for the record, an advocate of Microsoft 365 customers using AIP (sensitivity labels) in basically any circumstance it&amp;rsquo;s appropriate to do so.  So in this blog, I&amp;rsquo;ll counter the earlier post with three often overlooked useful things you can do with it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Three Considerations for Azure Information Protection Deployments</title>
      <link>https://campbell.scot/3-considerations-for-aip-deployments/</link>
      <pubDate>Sat, 15 May 2021 08:25:46 +0000</pubDate>
      <guid>https://campbell.scot/3-considerations-for-aip-deployments/</guid>
      <description>&lt;p&gt;Azure Information Protection (AIP) - more accurately exposed to Microsoft 365 now as &lt;strong&gt;sensitivity labels&lt;/strong&gt;- is close to the top of my favourite wins for securing your data in a Microsoft ecosystem.  While designing a detailed labelling and classification system is far from quick, it &lt;em&gt;is&lt;/em&gt; quick to get up and running with baseline policies that protect your confidential company data from getting read outside the company.  Simply by applying a sensitivity label that limits access to confidential data to users in your domain, you&amp;rsquo;ve covered a massive chunk of data loss scenarios.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Revoke Access to Office Files with Sensitivity Labels and Azure Information Protection</title>
      <link>https://campbell.scot/revoke-access-to-office-files-with-sensitivity-labels-and-azure-information-protection/</link>
      <pubDate>Thu, 08 Apr 2021 06:16:40 +0000</pubDate>
      <guid>https://campbell.scot/revoke-access-to-office-files-with-sensitivity-labels-and-azure-information-protection/</guid>
      <description>&lt;p&gt;Most of us have had that &amp;ldquo;oh &amp;lt; &lt;em&gt;blank&lt;/em&gt; &amp;gt;&amp;rdquo; moment where we have given someone access to someone only to immediately or later need to undo that access.  Azure Information Protection has historically been able to help us there.  AIP allowed us to create protected (encrypted) documents and also let us remove access.  However, in the move from &amp;lsquo;classic&amp;rsquo; AIP to the new &lt;strong&gt;unified labelling&lt;/strong&gt; with &lt;strong&gt;sensitivity labels&lt;/strong&gt;, the ability to revoke was lost in the transition.  Now it&amp;rsquo;s back in preview, but unlike the classic version, it&amp;rsquo;s managed on the client and not a web portal.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Microsoft Information Protection Sensitivity Labels - Custom User Permissions and Do Not Forward</title>
      <link>https://campbell.scot/microsoft-information-protection-sensitivity-labels-custom-user-permissions-and-do-not-forward/</link>
      <pubDate>Thu, 25 Feb 2021 15:02:30 +0000</pubDate>
      <guid>https://campbell.scot/microsoft-information-protection-sensitivity-labels-custom-user-permissions-and-do-not-forward/</guid>
      <description>&lt;p&gt;With Microsoft Information Protection, you can apply &lt;strong&gt;sensitivity labels&lt;/strong&gt; to files, emails, and containers such as SharePoint Libraries.  These labels apply &lt;strong&gt;protection&lt;/strong&gt; which, in the context of files and emails, really means &lt;strong&gt;encryption&lt;/strong&gt; using AES-128 or 256 (key size depends on file type).  The great thing about Information Protection is that you control an access control list of who is allowed to access the content and it&amp;rsquo;s managed as a cloud service by Microsoft.  The document or message, when opened, checks who is authenticated (who is signed to Outlook or the Office 365 app, for example) and only allows access if they have permission.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
