Microsoft Purview Sensitivity Labeling

0:00Sensitivity labels keep your content safe by making sure only the right people in your organization can edit it and also that you're following company policies and regulations. We're talking about content here. We're talking about teams. Our meetings. Along with chats files and emails. Let's say you and I work for an organization called would you ink.

0:31They say we have data throughout our infrastructure. They have to do a product launch announcements. Or maybe quarter to sales performance reports. Or customer contracts and pricing agreements. So many data here could be critical and very important and should be kept confidential. And sensitivity labels can help us accomplish this. So let's say we had these labels. We have public internal and also confidential.

1:01Let's say this data here. The product launch announcements. Is public information and available on our websites for anyone can get to it. Or in other words, there are no secrets here. So we could sign a public label to that data. Now our quarter to sales performance reports is a different story. Customers or the public should never see that. So maybe we assign that data a label of internal. Then we have customer contracts and pricing agreements.

1:34Which you can imagine should be kept confidential and away from prime ice. So maybe we assign this type of data a confidential label. So here any users there are assigned this internal label. We'll have the ability to see that sales performance report. Maybe your leadership team has access to that confidential label. And therefore they will be the only ones that would see that customer contract or pricing agreements data. So again, we're keeping our content safe by ensuring that only certain people can access certain data.

2:10So why are sensitivity labels important? We saw in a previous scenario they protect sensitive data. So we have the ability to apply encryption, apply watermarking, along with restriction actions by preventing the copying of any sensitive data. Sensitivity labels also ensure that any sensitive information is handled accordingly to any internal policies or regulations. We also can regulate or have control of access.

2:43So here we can control who can access the label content or maybe participate in label beings. These labels also provide visual indicators. So the user can see the label applied. So in the event that they see confidential, it allows that user to understand the sensitivity of the information they're handling. Our focus is Microsoft Teams. Sensitivity labels can be applied using several different key areas of the Microsoft environment for just focusing on teams.

3:17One of them being a team itself. So here we can control who can access all the content within that team. We can also use these labels to protect our meetings. We can't protect our meeting invites, along with the team's meetings and chat. Our sensitivity labels can also be used within SharePoint sites and also One Drive accounts. So for our users, any files that are shared in private chats are stored within OneDrive.

3:53Any files shared in a team channel are stored within SharePoint. So we can definitely use sensitivity labels to protect the data in both One Drive and also SharePoint. They can also be used in meeting templates. So a meeting template is a bunch of settings that are pre-configured for a meeting that user could use. So let's say this was our template here. Maybe this template has a sensitivity label of internal.

4:27When a user creates a meeting with this template, the label of internal is automatically applied to that meeting. And finally we can use sensitivity labels to encrypt our voicemail messages. Now the creation of these sensitivity labels is done through Microsoft PerView. So here we go on the solutions and on the solutions, the option that we want to go with is this information protection. Then we should see an option to create this sensitivity label.

4:58You and I would definitely do that in a future video. In order for the user's environment to be able to use these sensitivity labels, our first step is to create these labels. But then labels must be published via label policies to those users. To those users that will be using these labels. You also see documentation that these labels can be applied manually or automatically.

5:28So manually a user will select and apply and label themselves. So automatically as you would assume the user is not doing this, policies are used to determine if that data should be labeled or not based on certain criteria. As usual there is licensing involved. Let's go to a document here and now we show this link below this video. We have a section here, let me expand our table so it's easy to see.

6:03So we can see the licenses that are needed in order to enable manual sensitivity labeling. If we go back to our document here we see other licenses that are required for certain features. Like for schedule meetings, if we scroll down a bit, for team online meetings. And that's what I look for, the automatic sensitivity labeling. We can see that the license requirement is different for the automatic sensitivity labeling. So in this video we discuss sensitivity labels along with the functionality within Microsoft Teams, along with the licensing requirements.

6:41In the following video you and I will go to the creation of a sensitivity label . [BLANK_AUDIO]

0:00All right, next we'll go to the creation of a sensitivity label with the Microsoft purview. All right, here we go on the solutions. We'll go to information protection and we go on the sensitivity labels. All right, we see some here. The super top secret one is one that was playing with offline. So what we're going to do is create a label. We'll call this internal use only. We'll also give that the name or display name of the label.

0:32So name is what the admin will see in the admin portal. And display name is the name that your users will see. All right, so let's scroll down a bit. We see for label priority, there by default, this label of internal use only will have the highest priority. This comes into play for us. We have multiple sensitivity labels that could apply to a document or an email, for example. So here we can put a description for users.

1:02So I'll put that there so we can see what it says there. And for the demo, I'll do the same for admins. And I'll give it a color, that one there. And at this point, we're nuts. So next we have to define our scope. We'll determine both the settings that we can configure for a label and also where that label will be available to what apps and services. We see here that labels can be applied to data assets and also containers.

1:35And to explain what a container is, I have this slide. So Microsoft Teams, a team is treated as a container. So when you and I apply a sensitivity label to a team, we're setting the security and compliance controls for the entire team container, imagine individual measures or files. So meaning that our container includes items like the team itself, channel chats and posts, the associated SharePoint sites, those files stored in those team channels.

2:07And also the associated Microsoft 365 group, which really gives us the group membership to that team. So our data can be applied to files along with other data assets. So here we're talking about the files within the office applications, word, cell, PowerPoint, along with other Microsoft services. Our labels can also apply to emails. And our labels can also be applied to meetings. We also can apply labels to groups and sites. Now in your environment, this may be grayed out.

2:39And that would be because we have enabled sensitivity labels for containers. In the following video, we'll go over how we can enable sensitivity labels. So therefore groups and sites is an option for you. All right. So we'll go ahead and choose nuts. So here we can configure our protection settings. So one being control access. This setting is really for emails or media invites or documents. So here we're trying to prevent someone or really unauthorized people from accessing the data that has this label.

3:12We also have the ability to apply content marking. So here we can add watermarks, headers, or footers to content for our users when they're using the office applications. We also have protect team meetings and chats. So here we're going to label parent events team meeting options along with team chat. All right. We choose nuts. So let's be configured access control settings, which really allows us to enable you and I to define who can access these items. It does have this label assigned to it.

3:42And also what they can do with the content. So we have two options here. I SDM can assign the permission right now. So I know who exactly can access the content and what permissions they have when these labels apply. We also have the option to let the user decide. So whoever applies this label at that time can specify the access. Therefore, given that user that option and that's a baby. Or for now we'll keep the assigned permissions now. So here we can set a time limit for how long users can access the content.

4:15But never as you would assume did not expire. We can specify a certain date or a number of days after the labels apply. We also have allow offline access. So here folks will be able to open these files or content, even if their device is offline. I can choose never here requiring that user to be online to access that content . Or we can choose only for number of days. You would choose always. So next we'll assign permissions.

4:46So here we're going to specify what individuals or groups and the permissions they have. So here these users or groups are the folks that can open, edit content. It's a sign is labeled. From our demo, I'll pick two users. So I choose add users or groups. What I'm going to do is choose Pedro. We'll choose add. Let me add someone else. I'll pick Sierra.

5:18Choose add there. So this point I have two users. Also have the ability to modify their permissions. But you save. You can see those combinations of permissions is co-author. You also have the option to use dynamic watermarking. So what this would do is add the user's name to document as a watermark. So therefore discouraging any leaks or unauthorized sharing of that data.

5:51We also have double key encryption. So here we're adding an extra layer of encryption by requiring two keys to access that content. So one key is held by Microsoft and the other key is held by your organization. But for now I choose next. Now here we have different settings we can apply using a sensitivity label. Now you may already know what these settings do when we go over them later when we go through meeting posse. But for a demo I'm going to choose one. Just prevent copying and forwarding or meeting content.

6:23So we see here the participants will not be able to copy for meeting chat messages, links, live captions, transcripts or the content. All right. So we choose next here. We have the option to all the label files and emails but we'll skip that for now. We choose next. Here we have other protection settings. We have privacy and external user access. So here we can control if a team or group is public, meaning anyone can join or private. So let's go ahead and choose that one. We also have external sharing and conditional access.

6:57So here we can control labeled SharePoint sites or teams allow sharing with users outside of the organization. Then we have private teams discover ability and share content settings. Here we can do things like control if private teams are visible in search results. We choose next here. Now notice wherever options you choose here will influence what you'll see beneath here underneath groups and sites. So if I choose next here we see our options.

7:27So here for privacy we'll go ahead and mark the team as private. Let's look at external user access. Here we can allow group owners to add people outside of the organization. I'll leave that in check for now. We'll choose next. We'll go ahead and check this box. Therefore not allowing users to discover any private teams that have this label applied. And here we can control which type of teams can be invited into shared channels when using sensitive labels.

7:58So we have internal only to have our block and any external team. After those outside the organization for being invited to a shared channel. We also have same label only means the only team that have the same sensitivity label can be invited to a shared channel and also private teams. This blocks any public teams from being invited to a shared channel meaning only private teams can be used. All right for now we'll go ahead and choose internal only. We'll choose next. And at this point we'll go ahead and create our label.

8:31All right so we see this currently submitting. So we see here there are sensitive labels was created. In order for the sensitivity label to be used by users we have to publish these labels. So we definitely will do this later. For now I'll choose the uncreated policy yet and then we'll hit done. So now we'll scroll down a bit you see a new label called internal use only.

9:01So we notice here that we have a priority column. A priority is a time breaker. In the event we have two more labels that apply to the same object at the same time. So here the lower the number means a higher priority. In this section you now enter the creation of sensitivity labels. In the following video I want to go over what you need to do in the event that your groups and flights option that we saw earlier is grayed out.

9:35[BLANK_AUDIO]

0:00In this video, we'll talk about why the option groups and sites would not be available when you're creating a sensitivity label. Let's get started in 11. Previously, when you and I went to the creation of a sensitivity label, we have mentioned that this option here may be grayed out. There being groups and sites. We have a note here. To apply sensitivity labels to teams, SharePoint sites, and Microsoft 365 groups, you must complete these steps. These steps allow us to enable sensitivity labels for containers.

0:34Therefore allowing us to apply security settings at the team level. Remember, a team is treated as a container. So our container includes the team itself, for a channel and post, the associated SharePoint site with that team, to the file stored in that team, and also the underlying group membership, which is the Microsoft 365 group. You may also see this message here when we go to sensitivity labels with the Microsoft Preview, at the same message you and I saw in the previous step.

1:07So again, you may or may not see this message. But after we complete the steps that we're about to go through, what should happen is that you should no longer see that message in groups and sites should then be available. All right, so let's go here. All right, so the document that Microsoft takes you to is this one right here. So we choose this. So go ahead and click on here how to enable sensitivity labels for containers and synchronize labels. So we can see here all this is a one time procedure.

1:39So keep in mind someone before you might have done this already. So we have our first link here that will open up a new tab. And the first thing that we have to do is to enable sensitivity labels support with the Empire shell. So let's go to step number one here. If we haven't done so already, the first thing that we have to do is install the graph modules in order to run the command list in this documentation. Now Microsoft Graph is the API or an application programming interface from Microsoft that allows us to access data across different Microsoft 365 services.

2:19The Microsoft Graph connects to different services like Android E, Outlook, Teams, SharePoint, OneDrive. So here the first command installs the stable version of the Microsoft Graph module. And the second command here where it does versions install the beta version of the graph module, which we have newer experimental command letter features. All right, next we're going to connect to our tenant. Sorry about that. My pen jumped.

2:49Here we are connecting our session to Microsoft Graph. Then here we are requesting permission to read and write directory data like for example, users, groups. Also keep in mind here, you may be prompted to be authenticated. Now here for number three, we're going to fetch the current group settings to the Microsoft Entra organization and also display the current group settings. You can see here that we're creating a variable. We are retrieving directory settings. Let me scroll to the right here.

3:22We want to filter the output here to finally setting that has a property name, enable, and my P labels. This setting if true, sensitivity labels can be applied to Teams, groups, and SharePoint sites. Once, the sensitivity labels cannot be applied. We will see that when we run this command here, which is place the actual values of those settings. All right, I should run down a bit more. Now in the event, then no group settings were created for your organization, then you will get an empty screen.

3:58If that's the case, you didn't have to create those settings. So I just browse to this URL to see exactly how it's done. All right, so we'll scroll down a bit. We can see here, we have to install those same modules that we saw before. Then we'll go to this section, create settings at the directory level. This command will fetch or retrieve all available templates that define settings that we can apply at the directory level.

4:29Everything that we want to see the template, they are available that we can use to configure settings within the Microsoft 365 environment. If we scroll down here, we see the expectation of what we should see. Let me show you what happened to me. So you can see here, I ran that command, but unfortunately it did not give me the display name, as we can see right here.

5:02This could be because new versions of the graph beta module may have changed the output formatting, but no big deal because you can add this to the command format table with ID display name and description. And now we see we have the same information as we saw in our document. This group that unified is our settings template used to control Microsoft 365 groups across our entire directory. These Microsoft 365 groups are used behind a curtain for Microsoft Teams, for all of the group mailboxes, for SharePoint team sites, and that's the reason these templates use.

5:40All right, going down further, in this first line, what we're doing is finding the ID of that group unified template. Then here in our second line, we're getting the full template details by using that ID. So here, this variable is going to hold the ID that was found in the previous step. And here we see a screenshot of where I executed those same commands previously in my environment.

6:14All right, going down further. Here, we're creating a object that contains values to be used for that directory setting. What this is doing is creating a PowerShell hash table that is storing different parameters like the usage URL we see here. And also that parameter enable MIP labels. We're also going to set that to true. Therefore, enabling those system TIPD labels for Microsoft Teams and SharePoint sites. And further down, we're creating our directory setting.

6:47So here we're creating a new directory setting using the object params that we saw earlier. So once again, we have our template ID, which has the ID of that group that unified template in our organization. Then we have our two settings that we want to apply. All right, so I'm going to show you a screenshot. This is where I create that object. Now here, we're seeing the ID of the new setting that we just created.

7:18And also the template ID that was used to create that setting. So we can see here the template ends with three zero four B. And if I go to a previous slide, we can see the same ID here associated with that group that unified template. And next we want to read those values using these commands here. So in our first line, we're creating a variable.

7:48We are retrieving other current directory settings. But we want to filter the output with the display name is equal to group that unified. Then we want to see the values with those settings. And the output should look something like this. So we can see enable MIP labels. It's set to true. And we also have our uses guidelines URL fit to the URL that we defined earlier . So again, you may or may not have to perform these steps in the event going back to our original document.

8:22You ran this command, let it instead of getting output, you receive an empty screen. All right, going back to our first document that we looked at. But this points that one is complete. So next we have to synchronize our sensitivity labels to Microsoft inch righty. So we're doing a synchronizing these labels. They're available across different services like Microsoft teams, SharePoint, exchange, and also Microsoft intro. All right, so let's go over to this document to see what that looks like. All right, so let's go ahead and go step one.

8:55We have to import the module to manage a change of mine. Now documentation states that this is sending you in to the Microsoft purview security compliance center, which is not a Microsoft purview compliance portal. And I want to enter in our username. So in fact, let me show you a screenshot here. So here we see where I import the module is where I am logging into my session. Then once logged in, step two is not completed.

9:28Now we have to complete step three. And this command will synchronize our existing sensitivity labels from Microsoft purview into Microsoft intro ID. And we see that command right there. And doing so after period time, we'll make the group and sites option available when it comes to creating a sensitivity label. So in this video, one to the process of enabling sensitivity labels for our containers and also synchronizing those labels.

9:58Keep in mind that this may have been done ready by another member of your team in the past. But when I showed this process in the event that you're doing counter that the option is without or maybe you say not your lab environment. [BLANK_AUDIO]

0:00Next, you now go to the process of publishing our labels so they can be used by users. In the earlier video, we went to information protection, and then went to sensitivity labels, and we made one called internal use only. Now here, I can check that label, and I have the option here to publish label, and we see here that we're creating a policy. This policy is a label publishing policy.

0:30This policy defines how and to whom the sensitivity label are published. I'm going to hit cancel here, because I want to show you if we go to label publishing policy and go to publish label, we arrive at the same step here with the exception, we have to choose a sensitivity label. So here I can choose that internal use only , choose add, and now we're at the same place as we were before. All right, so here I'm going to do the next. I do have the option to assign this policy to an admin unit, if I wish, but it will keep for directory, two nets once again. So here I can apply this policy to all users and groups. For my demo, I'll go to edit.

1:11We're going to change this to specific users and groups. Let me go ahead and add a schedule here. I will also add Sierra. All right, we see we have to select it there, which is done and done again, which is nets. So we have several options here when it comes to this policy. So users must provide justifications to remove a label or lower specification. So in the event a user tries to remove a label altogether or replace it with a lower sensitivity or lower priority, the user will be prompted to give a reason. You also have required users to apply a label to their emails and documents. So here we're forcing that user once again to choose a label before they can save their document or send that email. Let's scroll down a bit here. We have required user to apply a label to their fabric and power BI content. And here we're just ensuring any sensitive data on our data analytics is protected just like our documents and emails and chats. The mail set provide users with a link to our custom help page. So here we can point to a page the user can go over. They

2:26can learn how we use labels in our organization. All right, so we choose nets here. We do have the ability to apply default label produce policy to different elements of the Microsoft environment. But for my demo, I'm going to stick with none. So for documents here, we choose none. The emails name is document. We have no inheritance, which is nets. This is for our meetings. So we don't have a default label for our meetings and calendar events. So we choose nets there. We also keep none for our sites and groups. Also choose nets here. And then we 're going to name this posse. And we'll name it our lab demo internal use only. All right , so we have nets and then we'll submit our policy. As we anything else, we have to hurry up and wait. So it says here, it can take up to 24 hours to publish these labels to the users that were assigned as policy, which was Pedro and Sierra. So at this point, we 'll go ahead and wait for his policy to take effect. And we'll jump into Pedro's and Sierra 's desk tops to see what they can do with their labels.

0:00All right, so in this video, we'll go ahead and go through a demo of our sensitivity labels in action. So in this scale, we did two things. One, create a sensitivity label, and then two, publish that label to users and groups. Before we jump into our demo, I want to point out two additional items. We'll go to solutions, back to information protection, and go to sensitivity labels. Here we go to our label that we created, and I'll choose edit here.

0:30So we choose nets here, nets again, one more time. I want to talk more about this section right here. This step here, we find what the label does. We'll write to these users have, or groups, when the label is applied to this content. So in this scenario, president's hero, have been applied, we call author permission. So this means any data that's labeled with this sensitivity label, these two users, Pedro and Sarah, we have co-authoring access. So we can think of this of who can do what when content is labeled with this sensitivity label. All right, so let's go cancel here.

1:11Let's go policies and to label publishing policies. So we choose the one that we created in the previous video, we'll go to edit policy. So here we have another section, here we go to edit here, we specify Sierra and Pedro. So this step here in our policy really defines who can see and apply the label in their Microsoft applications.

1:42So once again, Sierra and Pedro in my demo, I've debated to choose this label within their applications. So you can think of this as who has access to use this label within the apps. So I simply wanted to highlight the differences when it comes to assigning permissions within a sensitivity label versus assigning users to our label publishing policy. All right, so let's go to Sierra here, let's go toward the stop. When open up teams for like so, we'll go to calendar.

2:17Now here I'm going to create a new event like so. Let's go ahead and add a title here. So in our scenario, department reorgan ization. Now here I'm going to invite Thomas. Now also I'm going to invite Pedro. Now notice here I do have the option to apply a sensitivity label. So here we have internal use only and that's the one you and I created previously in the skill.

2:53And notice the description we see on left, going back to that sensitivity label , let me cancel here and go to sensitivity label, let's put that label of internal use only, I'll choose edit. Here we go down to description for users. This is what we see here. And that's what we also see for Sierra. We see our description right there. Now remember that this sensitivity label has a setting applied to it, which we'll see right here. So here we're preventing the copying and forwarding of mini content. Any participants in a meeting with this label will not be able to copy a four meeting chat messages, links, live captions or transcripts. So going back to Sierra.

3:44So here I'm going to change this to internal use only like so. So you can see our sensitivity label right there. So at this point I had sent. So now a little Thomas, we'll go to his teams, go to calendar, and then do the same for Pedro. All right, so we see our meeting there. So here I'm going to have Sierra start that meeting. So we should join. All right, so we have Pedro join also.

4:20Then we have Thomas join also. All right, so we see the all three folks are in that meeting. Let's say Sierra post a message. That message is being removing the HR department to Texas in September. So Thomas here, let me see that message. And say that's pretty juicy. Let me go ahead and copy this like so.

4:51And notice we have a message here due to policy. You can copy meeting chats. What happens to Pedro if he does the same thing with the right click copy and the same applies to him . But he's in being this meeting was created with that sensitivity label internal use only. And that was a setting that we set here when we created that sensitivity label. So imagine if you will, the different settings that we can apply to this label, which is later enforced with someone creates a meeting with this sensitive label. All right, going back to Sierra here, let's say she ends that meeting. All right, so that meeting is ended for everyone. So if I go back into her meeting. So we see information about the meeting invite, if we go to chat.

5:47We see a chat that we saw earlier. So if I do a right click here and copy, notice the same thing applies. So let's go Thomas, let's go back to our meeting . Notice here that Thomas cannot see the information because his meeting invite is protected by that sensitivity label. And Thomas is not assigned that internal use only label. In fact, if I try to go to chat here, the same thing should apply. If I go to copy, I do have the restriction there.

6:23Let's go back to Sierra. Let's say she wanted to create a new team. Should we go to chat? Then here, I can create a new team. So new team. So notice I can create a new team here. We'll call it reorg. So let's say wanted this to be public. And I tried to apply the sensitivity label of internal use only, nor is the public is grayed out. But only option here is private.

6:58And that's because going back to our sensitivity label, if I go nuts. Here, we say an option that the sensitivity label when used will always be set to private. So here are only team owners and members can access a group or a team. And only team owners can add additional members. So that's the reason that we're seeing this right here. All right, so we won't create that team there. So here we see the behavior that our user would expect in the event that a sensitivity label is applied to our team's meaning or during the creation of a team. But let me show you other scenarios where that sensitivity label will come into play. So let's say that Sierra creates a word document like so.

7:43So we're going to pay some content here. So imagine if you will, this was intended to be only seen by internal folks. So here the intention is not to have this document shared outside of the organization. All right, so I can do here is add a sensitivity label of internal use only. So we should see it updated right there. And I'm going to save this. So we do a save as. We also see descriptions here of this label. Let's go ahead and save this on my desktop for now. We'll call this project revamp like so. We'll hit save.

8:27So let's go teams here. Now I'm going to pick this sales department. Let me verify that the other users are indeed part of these teams. And we see everyone is a member here. So going back to our general chat. So let 's say I posted that file. Do we just created? All right, we're going to add, attach a file, upload from this device. We'll go to desktop and there's our file right there.

9:02We're going to go ahead and hit post. Remember now that Pedro and Sierra are the only two users that have access to that sensitivity label. So if I go to Pedro. So general chat, I see the document there. Let me attempt to open it to see what happens. And notice Pedro can definitely read that file. Why? Because he also has access to that sensitivity label. Let's pick someone else. Let's pick me, for example. Let's go to teams.

9:40We'll go to channels. General chat. What happens if I were to open this file? Notice I get this message here. I don't have permission to open this document. Why? Because I don't have access to that sensitivity label. All right, so let's also try email. Let's do Pedro this time. We'll go to email. We'll go to new email. Let's go and copy Thomas along with Pedro. Let the body and subject be super secret stuff.

10:19We'll copy that and put that as subject. But this time we're going to change this to internal use only. So we hit send. All right, so let's go to Sierra and wait for that email. While you're not waiting for that, let's go to Thomas and do the same. Let's go to his email. All right, so we see that email right there. Right, try to open it. So we see here, Pedro sent a protected message. So if I try to read that message, like so. So we see the message that I, being Thomas, do not have sufficient permissions to open that mail. Why? Because I do not have the sensitivity label required to read that email.

11:12If I go to Pedro and where I click on the email there, Pedro can definitely see the contents on that email because he does have that sensitivity label. And there we go. We saw a few examples of these sensitivity labels being used in Microsoft Teams and also in office applications, including Word and Outlook. [BLANK_AUDIO]

0:00For example, once again, I'm making it to the end of the skill. As always, we go through a bad asinception, where we have received some questions, but we're testing your knowledge. And our first question says, "Please refer to the image above when creating a sensitive label, which of the following is not an option when defining a scope?" All right, so we look at the image here, and let me zoom in. So why don't you provide a screenshot here in the event that question was not clear. The question is asin, "A blog of possible answers, which one is not an option listed here?"

0:34All right, so let's go ahead and close our image here. We have our options. Emails that have been one of them, groups and sites is, "One drive account," that doesn't sound right. We have meetings that is there along with files and other data assets. For the answer here is, "One drive account," we hit submit. Going to question number two, we also have another image. We refer to the image above, what impact does assigning permissions to a label have?

1:05All right, so just for clarification, if we look at our screenshot here, it seems they were creating a sensitive label, and we have the option here to assign permissions. So going back to our question, what's the impact of these settings? The answer to this question is this one. This step defines what the label does, really what rights users and groups have when it's labels apply to content.

1:36So we choose our correct answer and submit. Going down to question three here, we have yet another image, and the question is, "What impact does assigning users or groups to a label publishing policy have?" I don't have the word "have" here, but you'll see it by the time you get to this question. All right, so just for clarity, we're talking about when we're publishing sensitive labels. So let's look at our answers here. The correct answer being that this step defines who can see and apply the label in the Microsoft applications by teams the office applications like Word and Outlook, for example.

2:16I will pick a correct answer and hit submit. Then going to our final question here, folks report not seeing the newly advertised sensitivity labels when scheduling a team's meeting, which is a problem to be a possible cause. So our first possible answer that folks have unclear their team cache may be, but probably not. These folks haven't restored their computers after the last Windows update. That's not the answer. Check to see if the label was published by trading or adding it to a label publishing policy.

2:48That sounds good to me. And our final answer here is that the sensitivity label needs to be manually installed for the Microsoft Store. So we'll pick our correct answer and hit submit. So with that, our validation section is complete. I hope you did well, and I will see you in the next skill.