<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joanne Klein on Medium]]></title>
        <description><![CDATA[Stories by Joanne Klein on Medium]]></description>
        <link>https://medium.com/@joannecklein?source=rss-76436e897263------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*RlNKyL-MYRKwp7Wfh3sXeQ@2x.jpeg</url>
            <title>Stories by Joanne Klein on Medium</title>
            <link>https://medium.com/@joannecklein?source=rss-76436e897263------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 04:04:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@joannecklein/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Searching for unlabeled records in SharePoint]]></title>
            <link>https://medium.com/re-office-365/searching-for-unlabeled-records-in-sharepoint-d6d342d78ed1?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/d6d342d78ed1</guid>
            <category><![CDATA[search]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[retention]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Fri, 15 Jul 2022 03:37:24 GMT</pubDate>
            <atom:updated>2022-07-15T03:37:24.859Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MGL8wGlTIVMae2Fr69ktg.png" /></figure><p>Customers ask the best questions. Just last week, a customer asked if there was a way to show content on their site that DIDN’T have a retention label on it.</p><p>Sounds simple enough until you dig into the details.</p><p>Let’s not go happy path on the answer… let’s talk real world. Consider multiple libraries on a site, some potentially have multiple levels of folders, you haven’t defaulted a retention label, you haven’t covered off every edge case in your auto-apply label policies, you may be relying on end-users to manually apply a retention label, you’ve applied a non-record retention label that end-users have removed, or you have a combination of any of these.</p><p>At some point, the roles in your organization involved with managing records (records managers, information stewards, etc.) will want to understand where retention labels are being applied and perhaps more importantly, where they’re not. Building a modern page on the site with some search web parts seems like an integrated and scalable way of presenting the information to them so they can take further action when required.</p><blockquote><a href="https://docs.microsoft.com/en-my/microsoft-365/compliance/data-classification-content-explorer?view=o365-worldwide">Content Explorer</a> in the Data Classification feature will certainly show you where retention labels have been applied to content across all locations; however, it won’t show you where they haven’t been applied. The key benefit of Content Explorer is it extends beyond SharePoint and includes Exchange and OneDrive as well.</blockquote><blockquote>Building search solutions like this post is doing to show where retention labels have and have not been applied is a good approach in SharePoint as there are some limitations to Content Explorer that a SharePoint search solution will address:</blockquote><blockquote>- it can take up to 2 days for content to show in Content Explorer; however, Search results show much quicker (~15 minutes)</blockquote><blockquote>- an elevated level of permission is required to access the Content Explorer feature; however, for a search solution, records managers/information stewards only need access to the site(s) where the business records are stored and where the modern page is built</blockquote><p>I’m using the PnP Modern Search web parts for this solution. I’m not going to go over how to install and configure them in this post. Refer to this link for a great explanation of that: <a href="https://microsoft-search.github.io/pnp-modern-search/">Introduction — PnP Modern Search (v4) (microsoft-search.github.io)</a></p><p>The salient point of this post is defining the query to identify unlabeled documents. The PnP Search web parts are just one way of showing the results to the end-user.</p><blockquote>I wanted to use Microsoft search for the solution simply because of scale and the built-in permission model it provides. I struggled for awhile trying to build the query for 2 reasons:</blockquote><blockquote>I thought the ComplianceTag managed property (the property that holds the retention label name value) would be empty for unlabeled items and therefore not searchable in a query.</blockquote><blockquote>I wanted to build the query in such a way that as new retention labels were added over time, the query would continue to work without updates. With the help of Twitter, <a href="https://twitter.com/andrewjolly">Andrew Jolly</a> provided me the query to detect retention labels in a scalable way. Thanks Andrew!</blockquote><p>Note: this post assumes there are roles responsible for managing the business records on SharePoint site(s) that have an interest in knowing this information. This is typically the information steward role. The information steward could be in charge of a Hub of SharePoint sites (Finance Hub for example). This search solution will work for 1 site, many sites hubbed together, or even SharePoint tenant wide simply because of the scalability of Search.</p><p>For this post, I’ll build a modern page of “Unlabeled documents” on 1 SharePoint site. Let’s dig in.</p><p>Start by building a new Result Source on your SharePoint site by going to <em>Site settings… Site Administration…Result source</em></p><p>A result source is one way (there are others) of filtering the search results so you only get back what you’re interested in. For this post, that’s any file<strong> without</strong> a retention label applied. The most important part of a result source is the query you provide and test in the Query Builder. Using the alphabet with an asterisk as the retention label condition is what allows this query to accommodate any new retention labels that may be added to the system in the future.</p><p>Below is the query I used to get back all file types listed (you would need to include all that you need) that do NOT have a retention label applied:</p><pre>{searchTerms} <br>(filetype=docx OR filetype=xlsx OR filetype=pptx OR filetype=pdf)<br>NOT (<br>compliancetag:A* OR compliancetag:B* OR compliancetag:C* OR compliancetag:D* OR compliancetag:E* OR <br>compliancetag:F* OR compliancetag:G* OR compliancetag:H* OR compliancetag:I* OR compliancetag:J* OR <br>compliancetag:K* OR compliancetag:L* OR compliancetag:M* OR compliancetag:N* OR compliancetag:O* OR<br>compliancetag:P* OR compliancetag:Q* OR compliancetag:R* OR compliancetag:S* OR compliancetag:T* OR<br>compliancetag:U* OR compliancetag:V* OR compliancetag:W* OR compliancetag:X* OR compliancetag:Y* OR compliancetag:Z*) <br>SPSiteURL={SiteCollection.URL}*</pre><p>Below is the Query builder in the Result source configuration where you need to test the query:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*94gavcsCUSMyIM-z.png" /></figure><p>Once you have the result source, you can start building your modern page with the PnP search web parts on it. Here are the PnP search web parts available:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/457/0*Vuc3h8Lm4CJH9VFo.png" /></figure><p>I’ll start by adding the Search Results web part to a modern page and providing it the GUID of the ‘Unlabeled Documents’ result source built above:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/339/0*q11hRLVfRuo4KjND.png" /></figure><p>There are many settings you can use to customize the page and your results for your specific requirements. Add some filters to the page with the <em>Search Filters</em> web part to help describe the document such as who last modified it and a link to the library it’s stored in for further follow-up. Since search is permission-trimmed, granting your information stewards access to the site where the content is stored will allow them to see all search results.</p><p>For example, here is what my page looks like:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tRy3KHghLN0pR3KS.png" /></figure><h4>Closing thoughts</h4><p>Records Managers and information stewards will be interested in this type of information since they ultimately have the business unit/corporate responsibility for ensuring records are being managed appropriately.</p><p>This search page certainly does not preclude any automation capabilities you may have in place for applying a retention label which is still a scalable and recommended way for applying one; however, there will always be use-cases for needing to see what isn’t being labeled in case there’s something that hasn’t been detected and has fallen thru the cracks.</p><p>Thanks for reading.</p><p>JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d6d342d78ed1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/searching-for-unlabeled-records-in-sharepoint-d6d342d78ed1">Searching for unlabeled records in SharePoint</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Role Touchpoints during Information Governance and Records Management Implementation]]></title>
            <link>https://medium.com/re-office-365/role-touchpoints-during-information-governance-and-records-management-implementation-c35d87f6b8d1?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/c35d87f6b8d1</guid>
            <category><![CDATA[records-management]]></category>
            <category><![CDATA[information-governance]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[sharepoint]]></category>
            <category><![CDATA[governance]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Wed, 12 Jan 2022 06:33:37 GMT</pubDate>
            <atom:updated>2022-01-12T06:33:37.016Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HgulZ9AFTY7hqxFIIWBqJA.png" /></figure><p>I think about this a lot.</p><p>As I’m working with customers modernizing and implementing their information governance and records management (IG/RM) programs, I’m seeing a gap between several groups inside an organization. Depending on the size and maturity of the organization, the gap will vary; however, I see it to some degree in all customers I work with.</p><p>Understanding and then addressing the touch points between these groups can help to reduce the gaps.</p><p>I’ll broadly define the 3 <em>groups </em>I’m referring to for context…</p><h3>Group 1… SharePoint roles</h3><p>These are the roles responsible for the overall SharePoint Hub and Site architecture of an organization’s tenant. Since SharePoint has been around for a very long time, these roles often have a well-established SharePoint background extending back to previous SharePoint on-prem days. The responsibility of these roles typically includes the design and deployment of both site and tenant-level information architecture to support business processes. This usually extends into leveraging the site/tenant-level term store and configuring search.</p><p>A key responsibility for this role is involvement in the digitization of manual, legacy, or inefficient business processes when SharePoint is determined to be the appropriate platform to house it. This is where developers (both citizen and professional) enter the picture and have the opportunity to really make SharePoint “shine”.</p><p>Another key responsibility of this role group is to decide whether automation will be used for provisioning Microsoft Teams, Microsoft 365 Groups, or standalone SharePoint sites. This is an important decision to make for several reasons: consistency, manageability, support, and you guessed it… compliance.</p><p>This group covers a wide range of roles within; however most people in this group are usually concerned about the proliferation of SharePoint sites in their environment… typically something they historically had more control over in the SharePoint on-prem days.</p><h3>Group 2… Records Management roles</h3><p>This group is responsible for both information governance and records management for your organization and extends beyond what you may have stored inside a Microsoft 365 tenant. Like the SharePoint group, roles in this group are also from a well-established knowledge domain; however, the new “wrinkle” being added to this group’s formerly paper-based and dare I say simpler, digital world is the management of records inside the modern, digital workplace of Microsoft 365.</p><p>This group has a big job and responsibility on their hands. I’m witnessing a modernization of this knowledge domain and some new practices from both regulators’ and records managers’ perspectives.</p><h3>Group 3… IT Administration roles</h3><p>These administrative roles vary widely across organizations, but collectively are responsible for tenant-level policy configuration and enforcement, identity management, (some) storage management, assigning permissions, and any back-end technical configuration required to meet an organization’s needs. For this reason, the depth and breadth of tasks this group does will vary depending on an organization’s size, industry, culture, region, and team layout.</p><p>This group has gone through significant change from the on-premises days and some new Microsoft 365 admin roles have emerged as a result.</p><h3>The Touchpoints</h3><p>While operationalizing the IG/RM program inside an organization, each of the above groups typically have touchpoints with each other at certain times.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*6FCstis1bEBReT3o.png" /></figure><p>Here are some key tips for each of the touchpoints from an IG/RM implementation perspective:</p><h4>Records Management and SharePoint Role Groups</h4><ul><li>Tip 1: Understand Site/Information Architecture touch points with IG/RM</li><li>Tip 2: Include IG/RM roles during the Digitization/Modernization of business processes</li></ul><h4>Records Management and IT Administration Role Groups</h4><ul><li>Tip 3: IT Administrators need to “ramp up” their compliance knowledge</li><li>Tip 4: It helps for IG/RM teams to have a “compliance understanding” of Microsoft 365 architecture</li></ul><p>Each of the above 4 “tips” is a discussion on its own and is what I spend a good part of my consulting practice providing to customers.</p><p>Reach out to know more!</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c35d87f6b8d1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/role-touchpoints-during-information-governance-and-records-management-implementation-c35d87f6b8d1">Role Touchpoints during Information Governance and Records Management Implementation</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Protecting PII using Bundled and Named Entities]]></title>
            <link>https://medium.com/re-office-365/protecting-pii-using-bundled-and-named-entities-3468ef0e5e4a?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/3468ef0e5e4a</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[protection]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 06:52:31 GMT</pubDate>
            <atom:updated>2021-12-20T06:52:31.062Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SR6Heqg1bbbQPqiqp7gSlQ.png" /></figure><p>At Microsoft Ignite November 2021, 52 generally available sensitive information types (SITs) were added to the existing list of SITs. (<a href="https://techcommunity.microsoft.com/t5/security-compliance-and-identity/microsoft-information-protection-announcing-enhanced-automatic/ba-p/2871144">Microsoft Information Protection: Announcing Enhanced Automatic Classification Capabilities!</a>)</p><p>Included in these were 3 <em>Bundled Entities</em> built to look for full names, physical addresses, and medical terms and conditions. These 3 bundled entities are further separated out by country and industry into <em>Named Entities</em> to allow for country and industry specific regulatory and compliance scenarios.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*8NhVQMJH9vtEOp3u" /></figure><p>With privacy legislation being top-of-mind for organizations these days, I thought a practical use-case for these entities was to use them to detect and protect PII content with sensitivity labels.</p><blockquote><em>PII (Personally Identifiable Information) is information that, when used alone or with other relevant data, can identify an individual. Examples include: Full name, home address, email address, social security number, passport number, credit card numbers, date of birth, telephone number, IP address, etc.</em></blockquote><p>I’ll leverage the definition of the <em>All Full Names</em> and <em>All Physical Addresses </em>bundled entities as auto-apply conditions to identify some of the PII. Please know there is more PII than what these 2 bundled entities will detect so you should add additional sensitive information types targeting those pieces of PII in the auto-label condition as well.</p><p>Let’s dig in…</p><p>For demo purposes, I’ll create a sensitivity label called <em>Demo Label</em> and include an auto-labeling condition to recommend the sensitivity label with these conditions and message:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/840/0*f-0slqPaJVjWpB7u" /></figure><p>I’ll test with a document I know has some full names and physical addresses in it to see what happens. Whether I’m in the Word Online app or the Word Office app, I receive the sensitivity label recommendation based on detection of a full name and physical address as depicted in the 2 images below.</p><p>Note: in the Word app image, I clicked the <em>Show sensitive content</em> button to see the entities it has detected in the content from within the <em>Editor</em> fly-out pane.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rELa2JPnc6Ni6zIB" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/969/0*xgECSPhxLHpKNxVY" /></figure><p>You can gain insight on where these bundled/named entities are detected across Exchange, OneDrive, and SharePoint from <em>Content Explorer </em>inside the <em>Data Classification</em> feature (image). Use this information to inform your retention and protection policy configurations across your tenant:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/693/0*gUal5ne6mXJgIShs" /></figure><p>Other ways to use these named entities:</p><ul><li>test your content against these named entities to see if your content will match by selecting the named entity within the Sensitive <em>Information Types tab </em>in the <em>Data Classification</em> feature from the Compliance Center</li><li>include them as an auto-labeling condition to apply a sensitivity label to SharePoint and OneDrive content at rest (and Exchange email in transit)</li><li>use them in a Data Loss Prevention policy ( a great way to ensure you’re not leaking PII)</li><li>use them to auto-apply a retention label (a great way to retain/delete PII so you’re not over-retaining)</li><li>to address country-specific or industry-specific regulatory requirements, include the specific named entity, for example Australia Physical Addresses, for your condition rather than the full bundled entity</li></ul><p>My takeaway? Leveraging these named entities is a relatively easy way to protect PII content across your tenant. Have you tried them yet?</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3468ef0e5e4a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/protecting-pii-using-bundled-and-named-entities-3468ef0e5e4a">Protecting PII using Bundled and Named Entities</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Auto-apply Retention Labels via Business Trainable Classifiers]]></title>
            <link>https://medium.com/re-office-365/auto-apply-retention-labels-via-business-trainable-classifiers-ccab1df8e63f?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/ccab1df8e63f</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[retention]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Mon, 20 Dec 2021 06:52:14 GMT</pubDate>
            <atom:updated>2021-12-20T06:52:14.716Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aeMn5MrTblKoFCyPBjdSNw.png" /></figure><p>With the <a href="https://techcommunity.microsoft.com/t5/security-compliance-and-identity/microsoft-announces-the-general-availability-of-9-new-built-in/ba-p/3031209">recent announcement</a> of 9 new Generally available built-in ready-to-use Business trainable Classifiers inside Microsoft 365, I wanted to see how they might make my E5 customers’ lives easier retaining content across their tenant.</p><p>Up to this point in time, customers could build their own custom trainable classifiers to detect business-like content across their tenant (contracts, tax forms, loan agreements, etc.); however, these 9 new business trainable classifiers really hit the mark for the “typical” kinds of content they may have across their tenant without having to build one of their own!</p><p>Here’s the 9 new classifiers:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*BHy5Npb_zqueHkrc.png" /></figure><p>These trainable classifiers can be used to:</p><ul><li>classify/recommend/automatically apply sensitivity labels to items opened in Office client apps</li><li>automatically classify content and apply retention labels (<strong>what this post is about</strong>)</li><li>detect matching content in Communication Compliance policies</li></ul><h4>Advantages of this trainable classifier model</h4><ul><li>matching content can be automatically detected <strong>across your entire tenant</strong> and retention/sensitivity label applied if found</li><li>you don’t have to use other conditions to detect content (E.g., a Contract content type on a library or a specific Site URL) to use as an auto-apply condition on the retention label</li><li>if an end-user stores something in a site they aren’t supposed to, you can still apply a retention label if your auto-apply policy is scoped to all Sites, Microsoft 365 Groups, and OneDrives</li><li>you can detect/monitor when matching content is found in a communication channel — e.g., someone sharing Intellectual property with external parties</li></ul><p>Let’s check it out…</p><p>I’ll use a demo tenant to see if I can automatically detect agreements as defined by the ‘Agreements’ trainable classifier and apply a retention label if found!</p><p>Here’s the types of content the <em>Agreements</em> trainable classifier will look for:</p><blockquote><em>Detects content related to legal agreements such as Non-Disclosure Agreements, statements of work, loan and lease agreements, employment and non-compete agreements</em></blockquote><h3>Seeding some data</h3><p>Since statements of work (SOWs) are included in the <em>Agreements</em> trainable classifier, I’ll randomly seed some actual SOWs from my own company across several SharePoint sites to see if it will automatically apply a retention label when found.</p><p>Sample SharePoint Site A</p><ul><li>Created new ‘SOW Library’ and placed both Quote documents and SOWs in it</li><li>Created new ‘Regular Library’ and placed regular documents (non-agreements) and 2 SOWs in it</li><li>Added some SOWs into the default Documents library</li></ul><p>Sample SharePoint Site B</p><ul><li>Added some SOWs into the default Documents library</li></ul><h3>Retention Label and Policy Setup</h3><p>For this test, I created a new Retention Label, <em>Agreement</em>, and an auto-apply label policy called <em>Agreement Label Policy </em>statically scoped to ALL SharePoint sites and Microsoft 365 Groups<em> . </em>The label policy was configured to apply the <em>Agreement</em> retention label to all content matching the <em>Agreements</em> trainable classifier:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/914/1*EpFZHFHwqf4ADskZil_JtQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bgoWXuPJQgv3Uju4Rg2bvw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/947/1*sZBaQlkq_EIHmBlxKBDy-g.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/706/1*Je81EJhhRsFG0gg2fSgQBA.png" /></figure><h3>The Result</h3><p>An auto-apply retention label policy can take up to 7 days to apply the retention label; however, in this demo, the next morning the labels were applied to all matching content!</p><p>4 separate libraries across 2 SharePoint sites with SOWs stored in them had the Agreement retention label auto-applied by the retention label policy. Documents that weren’t detected as matches by the <em>Agreements </em>trainable classifier, did not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*_0M5jXru5kdpowu2azqVfA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/895/1*692Z15F7E35PiqFSsngiWg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/861/1*VvGR_Dws2-8UXWV08X-oMw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/873/1*E_VE4IKOAX1CESZou7Fwhg.png" /></figure><h3>Closing thoughts</h3><p>I think these nine built-in business trainable classifiers are a fantastic addition to allow you to automatically protect, retain, and monitor content across your tenant in an intelligent manner. This is another example of the value an E5 Compliance license provides in managing compliance at scale with no end-user intervention.</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ccab1df8e63f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/auto-apply-retention-labels-via-business-trainable-classifiers-ccab1df8e63f">Auto-apply Retention Labels via Business Trainable Classifiers</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Auto-Apply Retention Labels to Exchange Online Mailboxes (Archive)]]></title>
            <link>https://medium.com/re-office-365/auto-apply-retention-labels-to-exchange-online-mailboxes-archive-4d43a3d9bae3?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d43a3d9bae3</guid>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[exchange-online]]></category>
            <category><![CDATA[archive]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 13 Jul 2021 13:12:48 GMT</pubDate>
            <atom:updated>2021-07-13T13:12:48.285Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qxFy0CS16o3WFrjVkNe8Pg.png" /></figure><p>I received a great question from a reader the other day… “If I auto-apply a retention label to an Exchange mailbox, will it auto-apply the retention label to matching content in the Archive mailbox as well, if one has been enabled?”</p><p>I didn’t know the answer for certain so I set out to test it. :)</p><blockquote><em>In this post, I’m referring to a retention label configured in the Microsoft 365 Compliance Center and published to a user’s mailbox with an auto-apply condition.</em></blockquote><p>First things first… How do I know if a user has an Archive mailbox?</p><p>This can be done via PowerShell or thru the UI in either the Compliance Center (preferred) or the Exchange Online Admin Center. Link: <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/enable-archive-mailboxes?view=o365-worldwide">Enable archive mailboxes in the compliance center</a></p><p>Images below are where you see this setting in the Microsoft 365 Compliance Center. From here, you can enable/disable the archive at a single mailbox level or in bulk:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/871/0*S3nHUNjMuUnHXPQi.png" /></figure><p>You can see the usage across both the primary and the in-place archive mailboxes for all users where the archive has been enabled. I think this is an improvement over the UI in the EAC:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/585/0*1gMyb3CYsR2YdBrk.png" /></figure><p>To get at these same settings in the Exchange Online Admin Center, select <em>Manage mailbox archive</em> for a user’s maibox:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/0*hQAtaX7lfnyf_kL5.png" /></figure><p>Once enabled, you can see how much space is consumed by content in the archive mailbox:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/603/0*wbVSLX3qjOCBxjld.png" /></figure><blockquote><em>The in-place archive is different from the ‘Archive’ icon you see under a user’s primary inbox. The ‘Archive’ icon is a default folder in the primary mailbox. End-users can move content to the Archive folder to remove it from their inbox; however, it does not reduce the size of the user’s primary mailbox.</em></blockquote><blockquote><em>The In-place Archive, in comparison, is a separate mailbox for an end-user (circled in yellow below). It is not enabled by default, but once enabled can be used by retention policies as well as Outlook rules by the end-user. It will free up space in the user’s primary mailbox.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/364/0*nswyrbcdIYlubD2j.png" /></figure><p>Once I’ve enabled the in-place archive using any of the techniques above, I want to test if an auto-apply condition on a retention label will work on matching content across BOTH the primary and in-place archive mailboxes.</p><p>When testing auto-apply conditions in Exchange Online, you must ensure there is at least 10MB of content in the mailbox. To ensure this, I sent a number of test emails to Megan Bowen’s email address. I also moved at least 10MB of content into Megan’s in-place archive mailbox by selecting <em>Move to… In-Place Archive — Megan Bowen</em> from the menu.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/279/0*IX6FA0k_KAGl2Oh9.png" /></figure><p>To trigger the auto-apply condition, I seeded the text “Green Turtles” in a number of emails in both the user’s primary mailbox and their in-place archive.</p><p>I set up a sample retention label, <em>Sample Label</em>, and a label policy published to Megan’s mailbox with the auto-apply condition of “Green Turtles”:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/687/0*M7hLRR0P8ROSfo3_.png" /></figure><p>I waited for up to 7 days and checked the emails in both the primary mailbox as well as the in-place archive and BOTH had the <em>Sample Label</em> retention label applied:</p><p>User’s primary mailbox:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*VBREaMs42Ao3FxP-.png" /></figure><p>User’s in-place archive:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kN5NP8B9cx9nLdjY.png" /></figure><p>Let’s get back to the reader’s original question… “If I auto-apply a retention label to an Exchange mailbox, will it auto-apply the retention label to matching content in the Archive mailbox as well, if one has been enabled?”</p><p>Answer… yes! The auto-apply retention label will apply across both the primary and in-place archive for a user if the user’s mailbox account is included as a location in the label policy. :)</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d43a3d9bae3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/auto-apply-retention-labels-to-exchange-online-mailboxes-archive-4d43a3d9bae3">Auto-Apply Retention Labels to Exchange Online Mailboxes (Archive)</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Principles of Retention in Microsoft 365]]></title>
            <link>https://medium.com/re-office-365/principles-of-retention-in-microsoft-365-2b16b2cb3aea?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b16b2cb3aea</guid>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[governance]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 07:03:23 GMT</pubDate>
            <atom:updated>2021-10-06T17:05:43.204Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0Hvg25LszXBXtHcsQ-mXPA.png" /></figure><p>In Microsoft 365, there are 4 principles of retention to determine the retention and/or deletion outcome for a piece of content. For anyone implementing an overall information governance and records management program across Microsoft 365, it’s imperative to have an authoritative understanding of these principles.</p><p>The principles and the outcome they determine will guarantee you’re deleting content when you say you are and retaining content for as long as you’re required to meet your business, legal, and regulatory requirements.</p><p>This is important.</p><p><strong>**NEW</strong> Refer to this flowchart by Microsoft to demonstrate the logic used to determine the outcome for a piece of content: <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/retention-flowchart?view=o365-worldwide">Flowchart to determine when an item will be retained or permanently deleted</a></p><p>Over the past ~6 weeks, I’ve shared 6 scenarios to test your knowledge of the principles in a fun compliance challenge. I had great response from the community (Thank you!!) and a wide array of answers and follow-up questions. This demonstrated to me the need for more clarity around the principles which I hope I can provide.</p><p>To prove this is not <em>smoke and mirrors</em>, I’ve validated each of my answers by setting up a <em>Scenario Hub</em> in a demo tenant with the 6 scenarios configured in separate Modern Communication sites (and Exchange mailboxes where they were involved):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AHP63-765he9GQ5fxI19sQ.png" /></figure><p>Testing retention in Microsoft 365 can take days, weeks, or sometimes months to validate results. If you’re running tests of your own, my recommendation is to have a detailed plan before you start and then execute them in isolation to provide confidence in your results.</p><p>I’m now ready to start sharing the answers. For all answers, I’ll use the diagram below to identify which Principle of Retention LEVEL determines the retention/deletion outcome for each piece of content:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*YZ7MvVeUHQW5lo5d.png" /></figure><p>A few things to keep in mind while using the <em>Principles of Retention</em> diagram:</p><p><strong>3 Steps to take for EACH piece of content in the location…</strong></p><p><strong>Step 1</strong>: Create a list of all retention policies published to the location you’re evaluating (Exchange mailbox, SharePoint site, OneDrive account, Microsoft 365 Group, Teams chats/channel messages, Yammer messages) as well as any retention label that may be applied to the item in the location. At the time of this writing (July 2021), retention labels cannot be used across all locations where a retention policy can be.</p><p>Example list for SharePoint site 1:</p><ul><li>Retention Policy A set to retain for 2 years then delete and published to SharePoint site 1</li><li>Retention Policy B set to delete after 4 years and published to SharePoint site 1</li><li>Retention Label A set to retain for 7 years then delete and published to SharePoint site 1, applied to a document</li></ul><p><strong>Step 2:</strong> Start at LEVEL 1 of the Principles of Retention. Compare the list items from Step 1 against each other using LEVEL 1’s principle. If there’s a “winner” at the LEVEL, the comparisons stop. If there’s a tie, proceed to LEVEL 2’s principle for the comparisons. Continue this pattern, proceeding to the next level until a “winner” is determined.</p><p><strong>Step 3:</strong> Once you have a “winner”, it determines the retention and/or deletion outcome for the item.</p><h4>Deletion Policy or Retention Policy?</h4><p>If you’re getting started with retention features inside of Microsoft 365… whether a retention policy/retention label is configured to retain forever, only retain for a period of time, only delete after a period of time, or retain and then delete, they’re called retention policies/retention labels in the Microsoft 365 Compliance Center and NOT deletion policies/deletion labels.</p><p>I say this to highlight the point that even if it’s called a “Retention” policy, it may only be configured to delete something without having any kind of retention component.</p><p>Below are links to the original scenario questions and my “official” answers:</p><ul><li>Scenario 1: <a href="https://joannecklein.com/Scenario1">https://joannecklein.com/Scenario1</a> Answer: <a href="https://joannecklein.com/2021/07/05/principles-of-retention-challenge-scenario-1-answer/">Scenario 1 Answer</a></li><li>Scenario 2: <a href="https://joannecklein.com/Scenario2">https://joannecklein.com/Scenario2</a> Answer: <a href="https://joannecklein.com/2021/07/06/principles-of-retention-challenge-scenario-2-answer/">Scenario 2 Answer</a></li><li>Scenario 3: <a href="https://joannecklein.com/Scenario3">https://joannecklein.com/Scenario3</a> Answer: <a href="https://joannecklein.com/2021/07/09/principles-of-retention-challenge-scenario-3-answer/">Scenario 3 Answer</a></li><li>Scenario 4: <a href="https://joannecklein.com/Scenario4">https://joannecklein.com/Scenario4</a> Answer: <a href="https://joannecklein.com/2021/07/26/principles-of-retention-challenge-scenario-4-answer/">Scenario 4 Answer</a></li><li>Scenario 5: <a href="https://joannecklein.com/Scenario5">https://joannecklein.com/Scenario5</a> Answer: <a href="https://joannecklein.com/2021/08/29/principles-of-retention-challenge-scenario-5-answer/">Scenario 5 Answer</a></li><li>Scenario 6: <a href="https://joannecklein.com/Scenario6">https://joannecklein.com/Scenario6</a> Answer: <a href="https://joannecklein.com/2021/08/30/principles-of-retention-challenge-scenario-6-answer/">Scenario 6 Answer</a></li></ul><p>Thanks for joining in my fun Compliance challenge!</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b16b2cb3aea" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/principles-of-retention-in-microsoft-365-2b16b2cb3aea">Principles of Retention in Microsoft 365</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft 365 Fiscal Year Retention | Blog Post Series]]></title>
            <link>https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-blog-post-series-13f8d38f71cd?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f8d38f71cd</guid>
            <category><![CDATA[fiscal-year]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[retention]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 17:00:02 GMT</pubDate>
            <atom:updated>2021-06-29T17:50:25.690Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JTDk1Uvq5zLW2fIuNXQ0Zw.png" /></figure><p>Are you looking to implement retention based on Fiscal Year? This is a common requirement I see across many retention schedules. Records Managers are seeking to understand the different ways to accomplish this using the Records Management capabilities in Microsoft 365.</p><blockquote><em>A modernization of Records Management (RM) is currently underway with a shift in focus from exclusively ‘compliance and risk’ to also including how RM can better support the business on their digital transformation. A key piece to providing this support is to acknowledge a reliance on automation to meet their compliance needs rather than a manual approach of relying on the end-user to act as a surrogate “Records Manager”.</em></blockquote><blockquote><em>End-users have other work to get done.</em></blockquote><blockquote><em>I highly recommend downloading this AIIM eBook for reference: </em><a href="https://info.aiim.org/how-to-become-a-modern-records-manager-and-a-business-enabler"><em>How to become a Modern Records Manager (and a business enabler)</em></a></blockquote><p>The fiscal year retention requirement may read something like this… “Retain all Financial reports for 7 years past the close of the Fiscal Year they relate to and then destroy”.</p><p>There are several ways to accomplish this other than manually applying a retention label to a document. Remember… end-users have other work to get done (and aren’t Records Managers) and we don’t want to rely on them to have to remember to apply a retention label to a document at the end of each Fiscal Year. Instead, this blog post series will look at numerous ways Fiscal Year retention can be automated.</p><p>Each of the techniques I’ll describe will have differing levels of automation, control, complexity, pros, and cons. I’ll walk thru each of them end-to-end in separate posts published over the coming days/weeks and will link to them here:</p><ul><li>OPTION 1: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-default-folder-f7fbbf40f176">Microsoft 365 Fiscal Year Retention | Default Folder</a></li><li>OPTION 2: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-event-based-library-default-2b1d6bb0ebb5">Microsoft 365 Fiscal Year Retention | Event-based Library Default</a></li><li>OPTION 3: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-sharepoint-syntex-d924a984f982">Microsoft 365 Fiscal Year Retention | SharePoint Syntex</a></li></ul><blockquote><em>Advanced compliance capabilities will be required for each of the options in this series for “any user benefiting from the service”. This means anyone with contribute access or above to the document library where Fiscal Year retention is being applied will require the license providing the capability.</em></blockquote><blockquote><em>As of May 2021, one of these is required for any of these options: Microsoft 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Compliance, Microsoft 365 E5/A5/G5 Information Protection and Governance, Office 365 E5/A5. Refer to the </em><a href="https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#information-governance"><em>Security &amp; Compliance Licensing Guidance</em></a><em> for up-to-date detail.</em></blockquote><blockquote><em>FACT: Automation = Advanced licensing = Less onus on the end-user</em></blockquote><blockquote><em>… don’t shoot the messenger.</em></blockquote><p>Of course, the fiscal year model can be extrapolated to other time-based retentions (monthly, quarterly, calendar year) by making minor adjustments.</p><p>Thanks for reading and I hope you find the series helpful!</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f8d38f71cd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-blog-post-series-13f8d38f71cd">Microsoft 365 Fiscal Year Retention | Blog Post Series</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft 365 Fiscal Year Retention | SharePoint Syntex]]></title>
            <link>https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-sharepoint-syntex-d924a984f982?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/d924a984f982</guid>
            <category><![CDATA[sharepoint-syntex]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[event-based-architecture]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 16:58:20 GMT</pubDate>
            <atom:updated>2021-06-29T18:01:23.767Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g180ErA0Oo0SFyd0FxP7pA.png" /></figure><p>This is the third post in the Blog Post series, <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-blog-post-series-13f8d38f71cd">Microsoft 365 Fiscal Year Retention</a>, and its purpose is to demonstrate one of the ways you can implement Fiscal Year retention inside Microsoft 365.</p><p>The retention requirement may read something like this… “Retain all Financial reports for 7 years past the close of the Fiscal Year they relate to and then destroy”.</p><p>There are several ways to accomplish this other than manually applying a retention label to a document. Remember… end-users have other work to get done (and aren’t Records Managers) and we don’t want to rely on them to have to remember to apply a retention label to a document at the end of each Fiscal Year. Instead, let’s look at how this can be automated.</p><p>Each of the options in this series has differing levels of automation, control, complexity, pros, and cons. I’ll walk thru each of them in separate posts and will update the links here as they’re published:</p><ul><li>OPTION 1: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-default-folder-f7fbbf40f176">Microsoft 365 Fiscal Year Retention | Default Folder</a></li><li>OPTION 2: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-event-based-library-default-2b1d6bb0ebb5">Microsoft 365 Fiscal Year Retention | Event-based Library Default</a></li><li>OPTION 3: Microsoft 365 Fiscal Year Retention | SharePoint Syntex <strong>(this post)</strong></li></ul><blockquote><em>Advanced compliance capabilities are required for each of the options in this series for “any user benefiting from the service”. This means anyone with contribute access or above to the document library where Fiscal Year retention is being applied will require the license providing the capability.</em></blockquote><blockquote><em>As of May 2021, one of these is required for any of these options: Microsoft 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Compliance, Microsoft 365 E5/A5/G5 Information Protection and Governance, Office 365 E5/A5. Refer to the </em><a href="https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#information-governance"><em>Security &amp; Compliance Licensing Guidance</em></a><em> for up-to-date detail.</em></blockquote><blockquote><em>FACT: Automation = Advanced licensing = Less onus on the end-user</em></blockquote><blockquote><em>… don’t shoot the messenger.</em></blockquote><h3>Steps for Fiscal Year Retention | SharePoint Syntex</h3><p>This post will demonstrate how you can use a Document Understanding model to extract the Fiscal Year from an unstructured document, apply an event-based retention label to the document, and then trigger the event at the end of the Fiscal Year to start retention.</p><p>Please refer to a previous post of mine where I show how to build a Document Understanding (DU) model for a Statement of Work (SOW), <a href="https://joannecklein.com/2020/10/12/sharepoint-syntex-first-steps-with-intelligent-content-types-and-compliance/">SharePoint Syntex. First Steps with Intelligent Content Types and Compliance.</a> Once you’ve reviewed that post, come on back… I’ll be waiting. :)</p><p>In this post, I’ll add a custom column entity extractor for Fiscal Year to the DU model for the SOW and automatically apply an event-based retention label.</p><h4>This option involves 8 steps:</h4><ol><li>Create event-based retention label</li><li>Associate the retention label to the DU Model</li><li>Add term synonyms for each Fiscal Year term for months within the Fiscal year</li><li>Add a Fiscal Year entity extractor to the DU Model</li><li>Train the DU model with sample documents</li><li>Publish the DU model to all libraries across your tenant where SOWs will be stored</li><li>Validate the search query for the event</li><li>At Fiscal Year end… trigger the event</li></ol><p>Let’s dig in…</p><h3>Step 1 | Create Event-based Retention Label</h3><p>For this test, I’ll create a new event-based retention label called <em>FY Event Label.</em> I’ll associate it with an event type, <em>Fiscal Year End.</em> This event type has been previously defined and is a “container” for all labels that will be associated to the event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nq6UXLCtr6pWBwhK.png" /></figure><h3>Step 2 | Associate Retention Label to DU Model</h3><p>Once the retention label has been configured, you can associate it to the DU Model. You don’t have to publish the retention label to the Content Center to see it in the Retention label dropdown list.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/369/0*lAJMmr8TnKlyDeo4.png" /></figure><h3>Step 3 | Add Term Synonyms</h3><p>On the SOW documents I’m building the DU model for in this tenant, there is a line indicating when invoicing will start. (image)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/552/0*KZeNMzWCDdEu01Ly.png" /></figure><p>All SOWs where invoicing starts in a month of a Fiscal Year will require the retention period to begin after the Fiscal Year they relate to is over. I use term synonyms to accomplish this.</p><p>In the tenant term store, I’ll add a term set for Fiscal Year. For each Fiscal Year, I’ll add synonyms for every month in the year. The image below shows all Fiscal Months in the 2022–23 Fiscal Year added as Term synonyms (yellow rectangle):</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2LaPyXzaLVF0xoD_.png" /></figure><p>A SharePoint Syntex DU model will detect the term synonyms in the content of the document and automatically assign the parent term, Fiscal Year in this case, to the SharePoint column. For example, if ‘Sep 2022’ was detected in the document, the term 2022–23 would be set on the SharePoint column. This is key to making this work.</p><h3>Step 4 | Create Entity Extractor for Fiscal Year</h3><p>I want to extract the fiscal year from the SOW and I do this be defining an Entity Extractor for it in the SOW DU model. I’ve pre-created a Fiscal Year site column in the SharePoint Syntex content center and I use that to build the Entity Extractor from.</p><p><em>Tip: you must pre-create any columns that are of a managed metadata column type (TaxonomyFieldType).</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/331/0*Jnju1tG7R8cJiACN.png" /></figure><p>To train the model, you need at least 5 positive examples of an SOW and 1 negative example. Each of the sample SOW documents has a consistent string in it depicting the invoicing start month as follows:</p><p><strong><em>Invoicing begins: (MMM CCYY)</em></strong></p><p>I’ll use this to build the <em>explanation</em>. An explanation is like a tip to teach the DU model how and where to identify the entity you want to extract. You need at least 1 explanation for each entity extractor. I’ll teach the model to look for the phrase, <strong>(MMM CCYY)</strong>, before the entity within the starting 80 characters of the document and then extract the value following it into the Fiscal Year.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/747/0*CQ8KGpwMkiBnZ-x0.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/713/0*Au24Wcn2Q47dm-jk.png" /></figure><h3>Step 5 | Train the DU Model</h3><p>Once the explanation is configured, the model needs to be trained to predict what the Fiscal Year column will be. The first image below shows the source document and the content within extracted by the entity extractor and the second image shows the predicted values for the Fiscal Year entity extractor. The prediction is the value that will be inserted into the SharePoint column:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/742/0*zc2vdGBnVN7LC6Vd.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/575/0*pVTrfUH3_kAMuvkY.png" /></figure><p>You may be thinking that the Predictions above don’t look like Fiscal Years; however, once that value is added to the column in SharePoint, it will detect it is a term synonym and will correctly apply the main term, Fiscal Year 2020–21 in this case, to the SharePoint column.</p><h3>Step 6 | Publish the DU Model</h3><p>If you’ve got this far, you’re done the heavy lifting! Yay!! Now you need to publish the DU model to all libraries across the tenant that may have an SOW uploaded into it.</p><p>I have several SharePoint sites in this tenant that house SOWs. Below I’m showing a SharePoint site called <em>Finance Team</em> which I’ve published the DU model to. I’ve uploaded 9 SOWs and 2 documents that are NOT SOWs to see what happens when the DU Model runs against them.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*t0e0w2tQR7BwzNgK.png" /></figure><p>You can see all the metadata that was successfully extracted out of the documents, including the Fiscal Year. All columns extracted had a corresponding entity extractor defined in the DU Model. You’ll also notice the retention label, <em>FY Event Label</em>, has been successfully applied since it is associated to the SOW DU model.</p><p>I’ve placed a green star beside the 3 for FY 2020–21. This will be the year I’ll trigger the Fiscal Year end retention event for.</p><h3>Step 7 | Validate the Search Query</h3><p>The power of event-based retention comes in starting retention on content across your entire tenant. In this tenant, I have SOWs stored in several sites, each with a Fiscal Year assigned to it along with the retention label, <em>FY Event Label.</em></p><p>I want to determine how many items will be associated to the event. Using the same managed property configured in the last post, <a href="https://joannecklein.com/2021/05/25/microsoft-365-fiscal-year-retention-event-based-library-default/">Microsoft 365 Fiscal Year Retention | Event-based Library Default</a>, I run a search for the Fiscal Year and Retention label against all sites (from within the SharePoint app) with this query:</p><p>RefinableString108:”2020–21&quot; AND ComplianceTag:”FY Event Label”</p><p>The results span across 2 SharePoint sites (“The Works” and “Finance Team”) and returns 6 documents:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/664/0*z6aPPFuVYFJyHoRI.png" /></figure><h3>Step 8 | Trigger the Fiscal Yearend Event</h3><p>For this post, I’m manually configuring the event, however this can also be automated as described in my previous post. I’ll reference the retention label, <em>FY Event Label, </em>and use the same managed property mapping query as was used in my previous posts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/499/0*Gew8_1bqELQroDtC.png" /></figure><p>Several days later (controlled by a back-end process you have no control over), the event results are updated to reflect:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/0*B4j-T3wkSgVKRWKR.png" /></figure><p>After the retention period is complete, the backend process will complete the action you have configured on the event-based retention label. If this included a disposition review process, it will start; otherwise the documents will be automatically deleted.</p><h4>Pros</h4><ul><li>Scalable. Once the SharePoint Syntex DU model is configured, it can be published to any document library in your tenant. This will automatically extract the Fiscal Year metadata column and set the retention label. This will allow the annual event trigger to start the retention on the item.</li></ul><h4>Cons</h4><ul><li>You cannot add new content with the FY and the retention label AFTER the event has been triggered. It will not get picked up if you do. You must add a new event with the same search query to pick up the new content.</li><li>Someone has to remember to trigger the event! This can be done manually OR automatically (will incur technical debt that someone in your org will need to support)</li></ul><h4>Dependencies</h4><ul><li>Requires SharePoint search knowledge</li><li>Requires back-end configuration in tenant-level term store</li><li>Requires license for SharePoint Syntex</li><li>Requires SharePoint Syntex DU model configuration</li></ul><h3>Closing Thoughts</h3><p>The power of the SharePoint Syntex option is scale. If you have content you’re already processing with a DU model in many disparate sites across your tenant, this is a great option. The <em>heavy lift</em> is in the initial configuration; however, once that is done, each year only 2 things are required:</p><ul><li>ensure the new Fiscal Year term is added to the tenant-wide term store and include all of the months of the Fiscal Year as synonyms (assign a Term Set Owner to do this)</li><li>trigger the Fiscal Year event</li></ul><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d924a984f982" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-sharepoint-syntex-d924a984f982">Microsoft 365 Fiscal Year Retention | SharePoint Syntex</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft 365 Fiscal Year Retention | Default Folder]]></title>
            <link>https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-default-folder-f7fbbf40f176?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/f7fbbf40f176</guid>
            <category><![CDATA[event-based-architecture]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[compliance]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 16:58:10 GMT</pubDate>
            <atom:updated>2021-06-29T17:58:20.286Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cXDOeKkuyKf0zhCd_UIxHQ.png" /></figure><p>This is the first post in the Blog Post series, <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-blog-post-series-13f8d38f71cd">Microsoft 365 Fiscal Year Retention</a>, and its purpose is to demonstrate one of the ways you can implement Fiscal Year retention inside Microsoft 365.</p><p>The retention requirement may read something like this… “Retain all Financial reports for 7 years past the close of the Fiscal Year they relate to and then destroy”.</p><p>There are several ways to accomplish this other than manually applying a retention label to a document. Remember… end-users have other work to get done (and aren’t Records Managers) and we don’t want to rely on them to have to remember to apply a retention label to a document at the end of each Fiscal Year. Instead, let’s look at how this can be automated.</p><p>Each of the options in this series has differing levels of automation, control, complexity, pros, and cons. I’ll walk thru each of them in separate posts and will update the links here as they’re published:</p><ul><li>OPTION 1: Microsoft 365 Fiscal Year Retention | Default Folder <strong>(this post)</strong></li><li>OPTION 2: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-event-based-library-default-2b1d6bb0ebb5">Microsoft 365 Fiscal Year Retention | Event-based Library Default</a></li><li>OPTION 3: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-sharepoint-syntex-d924a984f982">Microsoft 365 Fiscal Year Retention | SharePoint Syntex</a></li></ul><blockquote><em>Advanced compliance capabilities are required for each of the options in this series for “any user benefiting from the service”. This means anyone with contribute access or above to the document library where Fiscal Year retention is being applied will require the license providing the capability.</em></blockquote><blockquote><em>As of May 2021, one of these is required for any of these options: Microsoft 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Compliance, Microsoft 365 E5/A5/G5 Information Protection and Governance, Office 365 E5/A5. Refer to the </em><a href="https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#information-governance"><em>Security &amp; Compliance Licensing Guidance</em></a><em> for up-to-date detail.</em></blockquote><blockquote><em>FACT: Automation = Advanced licensing = Less onus on the end-user</em></blockquote><p>Of course, the fiscal year model can be extrapolated to other time-based retentions (monthly, quarterly, calendar year) by making minor adjustments. A table at the end of each post will show the adjustments required for other time periods.</p><h3>Steps for Fiscal Year Retention | Default Folder</h3><h4>Step 1: Create retention label</h4><p>Create a retention label with your retention requirements. In this post, a retention label, <em>Test Review Label</em>, is created to retain for 1 year (2 days for my test) from <strong>date labeled</strong> then trigger a disposition review. (optional). By starting the retention period based on when the items are labeled, this provides you the control to start the retention clock.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/0*crvy-w-2uvMfje3K.png" /></figure><p>The retention label is published to the SharePoint site(s) containing the content requiring the Fiscal Year retention.</p><h4>Step 2: Create Fiscal Year folders</h4><p>Anywhere you have content requiring retention based on FY, you need to be able to identify that content at a FY level. I’m choosing to organize my content into FY folders in a document library rather than FY metadata. Does it have to be done this way? No, however for this option it provides a significant advantage by allowing you to easily control <em>when</em> the FY retention label is applied to content within the FY folder. You simply apply the retention label to the FY folder and all content within inherits the retention label. (This leverages the <em>default retention label</em> capability which requires an advanced compliance license).</p><blockquote><em>If you’d rather use Fiscal Year metadata to drive retention, check out the other options in this series.</em></blockquote><p>I’d recommend creating the FY folders in advance. You can do this either manually or automatically at the end of each FY. I’ve automated this process using Power Automate for Finance teams and have previously blogged about this here: <a href="https://joannecklein.com/2019/07/24/a-case-for-controlled-folders-using-microsoft-flow-with-retention/">A Case for Controlled Folders using Microsoft Flow (with Retention!)</a></p><p>Here’s a SharePoint site, <em>Blog Test Site 1,</em> with a <em>Financial Reports</em> document library with the FY folders created within it:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/0*zgKeW56Gu0B5WK8C.png" /></figure><p>Note: an alternative is to apply the Fiscal Year Retention label to each document either manually or with a Power Automate flow AT THE END OF THE FISCAL YEAR. Although possible, this is not practical for most organizations; however, this technique would not require an advanced license since the retention label would be manually applied to each document.</p><h4>Step 3: Apply the Retention Label</h4><p>At the end of each Fiscal Year, the retention label could be applied to the Fiscal Year folder using 1 of 2 methods:</p><ul><li>Manual method: set up an annual reminder for an administrator to apply the label to the folder. Due to the frequency of the reminder (once per FY), this may be a reasonable, albeit not perfect, approach. This method requires some governance around the process.</li><li>Automated method (PREFERRED): automatically apply to the FY folder thru a Power Automate Flow. This guarantees it will happen in an automated way and does not rely on human intervention.</li></ul><p>Once the retention label is applied to the folder, it’s automatically propagated to all content within, including subfolders and their documents if there were any, and retention begins starting from the labeled date.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/834/0*E3Jewv7BFYm02lXA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/854/0*Q9rsrFhjofjw-VZl.png" /></figure><p>If you had a disposition review configured for your label, disposition reviewers would receive an email notification with a link to the list of records at the end of the retention period. In this example, the documents within the FY folder are now awaiting my disposition. Alternatively, they can be automatically deleted… a choice dictated by your regulatory and business requirements.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*h6zCn6D7yv3BrWq4.png" /></figure><h3>Pros to this option:</h3><ul><li>Relatively simple to setup</li><li>Throughout the fiscal year, end-users can collaborate as they normally would while working with the current FY content (can be a pro and a con).</li><li>Because you’re controlling when the retention label gets applied, you’re controlling when the retention clock starts ticking… in this case, at the end of the Fiscal Year</li></ul><h3>Cons to this option:</h3><ul><li>Prior to the retention label being applied, end-users can easily delete content within the FY folder without having to first remove the retention label (can be a pro and a con), however this action is audited and the content follows normal recycle bin processing.</li><li>Since this options relies on the default retention capability for a folder, it requires a controlled folder structure for FY. I’ve seen this used on Finance teams where they are typically working on content relating to a Fiscal Year and are usually organized within their document libraries in this fashion already</li><li>Ideally requires a controlled (I.e. automated) process for applying the retention label to the FY folder although this can be done manually</li></ul><blockquote><em>Tip: in some document libraries, it may be advantageous to turn off the ability for end-users to create folders if you’re wanting to control the folder structure. This is an advanced library setting.</em></blockquote><h3>Extrapolate this option to other Time Periods</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*_QizDBBgpAKRcHAR.png" /></figure><p>My gift to you for reading all the way to the end of my post is to tell you what the next one in the series will be… 😊</p><p>Check out the next post in this series where an event-based retention label is set as a library default and we use Fiscal Year metadata to help automate this at-scale!</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f7fbbf40f176" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-default-folder-f7fbbf40f176">Microsoft 365 Fiscal Year Retention | Default Folder</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Microsoft 365 Fiscal Year Retention | Event-based Library Default]]></title>
            <link>https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-event-based-library-default-2b1d6bb0ebb5?source=rss-76436e897263------2</link>
            <guid isPermaLink="false">https://medium.com/p/2b1d6bb0ebb5</guid>
            <category><![CDATA[compliance]]></category>
            <category><![CDATA[retention]]></category>
            <category><![CDATA[microsoft-365]]></category>
            <category><![CDATA[event-based-architecture]]></category>
            <dc:creator><![CDATA[Joanne Klein]]></dc:creator>
            <pubDate>Tue, 29 Jun 2021 16:58:02 GMT</pubDate>
            <atom:updated>2021-06-29T17:59:32.532Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hIb17t8sM6UVayymkdbhyw.png" /></figure><p>This is the second post in the Blog Post series, <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-blog-post-series-13f8d38f71cd">Microsoft 365 Fiscal Year Retention</a>, and its purpose is to demonstrate one of the ways you can implement Fiscal Year retention inside Microsoft 365.</p><p>The retention requirement may read something like this… “Retain all Financial reports for 7 years past the close of the Fiscal Year they relate to and then destroy”.</p><p>There are several ways to accomplish this other than manually applying a retention label to a document. Remember… end-users have other work to get done (and aren’t Records Managers) and we don’t want to rely on them to have to remember to apply a retention label to a document at the end of each Fiscal Year. Instead, let’s look at how this can be automated.</p><p>Each of the options in this series has differing levels of automation, control, complexity, pros, and cons. I’ll walk thru each of them in separate posts and will update the links here as they’re published:</p><ul><li>OPTION 1: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-default-folder-f7fbbf40f176">Microsoft 365 Fiscal Year Retention | Default Folder</a></li><li>OPTION 2: Microsoft 365 Fiscal Year Retention | Event-based Library Default <strong>(this post)</strong></li><li>OPTION 3: <a href="https://regarding365.com/microsoft-365-fiscal-year-retention-sharepoint-syntex-d924a984f982">Microsoft 365 Fiscal Year Retention | SharePoint Syntex</a></li></ul><blockquote><em>Advanced compliance capabilities are required for each of the options in this series for “any user benefiting from the service”. This means anyone with contribute access or above to the document library where Fiscal Year retention is being applied will require the license providing the capability.</em></blockquote><blockquote><em>As of May 2021, one of these is required for any of these options: Microsoft 365 E5/A5/G5, Microsoft 365 E5/A5/G5 Compliance, Microsoft 365 E5/A5/G5 Information Protection and Governance, Office 365 E5/A5. Refer to the </em><a href="https://docs.microsoft.com/en-us/office365/servicedescriptions/microsoft-365-service-descriptions/microsoft-365-tenantlevel-services-licensing-guidance/microsoft-365-security-compliance-licensing-guidance#information-governance"><em>Security &amp; Compliance Licensing Guidance</em></a><em> for up-to-date detail.</em></blockquote><blockquote><em>FACT: Automation = Advanced licensing = Less onus on the end-user</em></blockquote><h3>Steps for Fiscal Year Retention | Event-based Library Default</h3><p>This option is comprised of 4 key components:</p><ol><li>An event-based retention label</li><li>A tenant-level Fiscal Year term set</li><li>A managed metadata Fiscal Year custom column</li><li>An event trigger at the end of each Fiscal Year</li></ol><p>You may be thinking… why not use the built-in <em>Compliance Asset Id</em>? Although it is certainly possible to use the <em>Compliance Asset Id for</em> event-based retention, I prefer to use a custom column to provide more rigor and control over the values entered into the column. For this post, I’m using a custom managed metadata column for Fiscal Year instead.</p><p>The “heavy lift” for this configuration is the initial setup. On subsequent fiscal years, you only need to ensure the fiscal year is being set on content across your tenant, the retention label assigned, and the fiscal year end event is triggered.</p><p>Let’s dig in…</p><h4>Step 1 | Create Term Set for Fiscal Year</h4><p>By using a tenant-wide managed term set to define your Fiscal Years, it provides the flexibility to use the term set in columns across all SharePoint sites in your tenant in a consistent way. This is particularly important if you have Fiscal Year content spread across numerous SharePoint sites, all requiring retention.</p><p>For anyone in the Records Management space, it’s important to understand how SharePoint managed terms, specifically tenant-level terms, can be leveraged to automate your retention schedule across SharePoint sites in a more scalable way than other metadata options.</p><p>We start by creating a tenant-wide term set for Fiscal Year in the Modern Term store.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*iH1bh-KKULq7Mo7w.png" /></figure><blockquote><em>Tip for Term Set Administration: Assign an owner to keep your term sets up to date and to update the default value as required. For the Fiscal Year term set, you may want to update the default value at the start of each fiscal year on all libraries consuming it.</em></blockquote><h4>Step 2 | Create an Event Type for Fiscal Year End</h4><p>Create an event type (mine is called “Fiscal Year End”) to identify the event for the end of the Fiscal Year (FY). The name should describe the event that will eventually be associated with an event-based retention label. At the end of each FY, we’ll create an instance of this event type with the exact details of the FY we want to start retention on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/597/0*4Q3EzazZeI__ZUWP.png" /></figure><h4>Step 3 | Create Event-based Retention Label</h4><p>Create a retention label with your specific retention requirements for the Fiscal Year content you want to retain. In this post, my retention label is called ‘Finance Report TEST’ and it is configured to retain for 3 days with a disposition review. I associate it to the <em>Fiscal Year End</em> event type from the previous step and publish it to the SharePoint site(s) where my Fiscal Year content will be stored.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/758/0*NJiIdpVK7Q6T_gd-.png" /></figure><blockquote><em>In Public Preview, you can now have a multi-stage disposition review. In this FY retention example, the first stage could be a Finance team and the second stage could be the Records Management team as the image below shows. Check out this blog for more details: </em><a href="https://techcommunity.microsoft.com/t5/security-compliance-and-identity/announcing-multi-stage-disposition-in-microsoft-records/ba-p/2361849#announcemultistage"><em>How to configure multi-stage disposition review</em></a></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/958/0*Nc88JLMKAEA1gMLW.png" /></figure><h4>Step 4 | SharePoint Document Library and Site Column setup</h4><p>For the retention engine to find the documents at the end of the Fiscal Year, the Fiscal Year must be associated to each document in any library where you want the retention to occur. Create a managed metadata site column, <em>FiscalYear</em> in my example, pointing to the tenant-wide term set created in step 1 and add it to the document library. To ensure it is updated on each document, do either 1 of these 2 things:</p><ol><li>Set the list column default for <em>FiscalYear</em> to be the current fiscal year. This will automatically set it to the current year for any document added to the library. This does not prevent an end-user from changing the value if required (if they entered a document for last Fiscal Year). If you choose this way, assign an administrator to set the default at the start of each Fiscal Year.</li><li>Optionally, and what I’ve done in this post, create Fiscal Year folders in the library and set the column default value for the <em>FiscalYear</em> column for each Fiscal Year folder. You can precreate these folders in advance for many Fiscal Years ahead. This will automatically set the Fiscal Year column to the default value for the folder the document is placed into. This is done in the library settings under <em>Column Default Value Settings</em></li></ol><p>This allows you to set the default term for the folder. In this image, I’m setting the default value for the FiscalYear column in the <em>FY 2019–20 </em>folder to be the 2019–20 term:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/623/0*8mkBTMRY5uXFMsc_.png" /></figure><p>Once you have all folders’ default value set with the correct term, you will see a green gear icon on each folder icon:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/835/0*jBx0qAGkWEIIZKSi.png" /></figure><p>Whichever way you choose to default the Fiscal Year, as long as the document’s Fiscal Year column has been filled with a value on each document, the retention engine has something to work with!</p><p>Last, but certainly not least, set the default retention label on the library to be the event-based retention label, <em>Finance Report TEST. </em>Know that once you do this, no document can be deleted unless the retention label is first removed from the document.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/864/0*cp3z9D9edzuBQfU8.png" /></figure><h4>Step 5 | Search Schema Preparation</h4><p>Because event-based retention is search-based, we need to do some pre-work in the SharePoint Search schema before triggering the first Fiscal Year event. This setup only needs to be done once and it can then be used in all future events and anywhere you want to use the Fiscal Year value across the entire tenant.</p><p>To start, we need a crawled property generated for the <em>FiscalYear</em> column. To do this, we add some sample content into the Fiscal Year folders in the library and wait for the content to be crawled by the search process.</p><p>Once the crawled property is generated, <em>ows_taxId_FiscalYear</em> in my case, I map it to one of the pre-configured RefinableString managed properties in the search schema, <em>RefinableString108 </em>in my example:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/921/0*xArGSKzUo62h9MBc.png" /></figure><blockquote><em>You MUST use a pre-configured Refinable managed property. A custom managed property will not work as the condition on an event trigger. Trust me, I’ve tested this!</em></blockquote><blockquote><em>Tip: Since I’m working in the tenant-level search schema, the managed property I’ve configured can be leveraged in other scenarios as well. For instance… use it in a Highlighted Content Web Part on a modern SharePoint page to show “Board Member bio pages filtered by current Fiscal Year”.</em></blockquote><h4>Step 6 | Validate the Search Query</h4><p>It’s always a good idea to test out your search query to verify the results before creating your event. In this case, I want to simulate the Fiscal Year End event for FY 2020–21 where I will be providing a query to determine all content to start retention on.</p><p>I’ll use the managed property in my query… <em>RefinableString108:’2020–21&#39; </em>and confirm there are 6 document results to be included in the retention event.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/696/0*MDZkf6UYMaG-ww2x.png" /></figure><h4>Step 7 | Create Retention Event</h4><p>At Fiscal Year end, after all documents worked on throughout the year have been tagged with the Fiscal Year they relate to, we need to trigger the event. We specifically want to start retention on anything with the <em>Finance Report TEST </em>retention label applied and the Fiscal Year 2020–21. This can be done several ways:</p><ol><li>Manually thru the UI, which may be a feasible option since this is only an annual event. This is what I’ve done for this post.</li><li>Automatically using:</li></ol><ul><li>PowerShell: <a href="https://docs.microsoft.com/en-us/powershell/module/exchange/new-complianceretentionevent?view=exchange-ps">New-ComplianceRetentionEvent (ExchangePowerShell)</a></li><li>REST API: <a href="https://docs.microsoft.com/en-us/microsoft-365/compliance/event-driven-retention?view=o365-worldwide#automate-events-by-using-a-rest-api">Automate events by using a REST API</a></li></ul><p>After you provide a unique event name, such as <em>Financial documents for FY 2020–21</em>, you must identify the settings for the event:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8a695sRmiYc3NAlq.png" /></figure><blockquote><em>If you select Use Event Type, it will process all content tagged with all retention labels associated to that event type. A use-case for this is if you have content with different retention periods, but all starting their retention at the end of the Fiscal Year.</em></blockquote><blockquote><em>If you select Use Existing Labels, you can select a myriad of event-based retention labels, each associated to potentially different event types. I’m still trying to come up with a good use-case for this scenario… if you have one, let me know! :)</em></blockquote><p>Immediately after I create the event for FY 2020–21 by supplying the event-based retention label, the search query to use, and the date to start retention, the counts are 0:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/750/0*2TDeNMiAGITCkaTW.png" /></figure><p>Several days later (when the back-end process has ran against the content), the counts are updated:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/492/0*2RYHazf4ZUKh4fjs.png" /></figure><blockquote><em>A new column, Label Event Date, is automatically added to the library once the back-end event process runs and has identified the content relating to the event. The date/time shown will match what was entered for the event trigger.</em></blockquote><blockquote><em>Important: if content is added AFTER the event date for the retention label and same Fiscal Year, 2020–21 in our case, the items will NOT be processed. You must trigger another event with the same conditions to pick up the new items.</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/946/0*BznHJrrZ4AmOYAUz.png" /></figure><h4>Step 8 | Perform Disposition Review</h4><p>Because I also had a disposition review configured for this retention label, I received an email when the disposition review period was reached:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/900/0*HTPNiSyfC3ByvKyl.png" /></figure><p>… and when I click <em>Go there now…</em> I see the 6 records waiting my review:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LiD2HbiwMpNZlwQx.png" /></figure><p>That’s it! The first year is the heavy lift on the setup; however, on subsequent years, this is all you will need to do:</p><ul><li>ensure you’ve set up the new Fiscal Year term in the tenant-level term set</li><li>ensure the default value for the current FY is set on libraries across your tenant where FY content will be stored. Although not required, it will make it easier on end-users working with the content if the value is defaulted for them</li><li>trigger the event at the end of the FY (automate if you can)</li></ul><h4>Pros</h4><ul><li>Scalable. As long as a Fiscal Year metadata column is populated on content and it has the event-based retention label assigned to it, the event trigger will start the retention on the item when you trigger the event.</li><li>Can set the default value on libraries to alleviate the end-user from having to do it [Optional]</li></ul><h4>Cons</h4><ul><li>Requires SharePoint search knowledge</li><li>Requires back-end configuration in tenant-level term store</li><li>You cannot add new content with the FY and the retention label AFTER the event has been triggered. It will not get picked up if you do</li><li>Someone has to remember to manually trigger the event OR you have to automate the process (which incurs technical debt)</li></ul><p>Please join me in the next post in this series where I use a SharePoint Syntex AI Model to automate the metadata extraction for Fiscal Year and automatically set the event-based retention label.</p><p>Thanks for reading.</p><p>-JCK</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2b1d6bb0ebb5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/re-office-365/microsoft-365-fiscal-year-retention-event-based-library-default-2b1d6bb0ebb5">Microsoft 365 Fiscal Year Retention | Event-based Library Default</a> was originally published in <a href="https://medium.com/re-office-365">REgarding 365</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>