When Was a Team Accessed?
Let’s say you have gotten this far using native Microsoft 365 functionality with SharePoint development. You’ve run your permission report, you’ve researched your security groups and nested groups, and you’ve cross-referenced that with a permission report that’s tens of thousands of lines long. Now, you’re finally able to report back to your security teams about who had access to sensitive information in Microsoft 365 and Microsoft Teams.
They might say, “Great, this is really helpful information. It looks like a few external users inadvertently had access to sensitive information against our policy. Can you tell us if they accessed it and when? Also, is this exposure level better or worse than last year’s?”
You let out a long and weary sigh — it looks like your quest isn’t quite over. You covered the who, what, and where. Now it’s time to tackle the when.
To understand what risky activity may be taking place and who has viewed these documents. And when, you’ll need to pull audit reports that surface user activity. And show you who has access to your content. While these logs are relatively easily to locate in the report section. Of the Microsoft 365 admin center. Keep in mind this is now the third report you’re cross-referencing.
Furthermore, each time you go through this exhaustive process of cross. Referencing all three reports, it’s still only going to give you a comprehensive. Snapshot of your sensitive information exposure. And its potential risk to your organization. That means that, in order to stay up to date. The process will need to be repeated again and again at a frequency. That meets your organizational requirements.
How to Tell Why a Team Exists?
Microsoft 365 allows you to either enable or disable external sharing across the tenant — the same with guest user access. While you do have the option to create specific policies for specific Microsoft Teams. SharePoint sites, and other workspaces, it is a tedious and time-consuming process.
To create appropriate controls for each workspace, some organizations use a controlled Microsoft Teams. Provisioning process wherein all Microsoft Teams creation requests are sent to IT for approval. However, it’s not that straightforward. For IT to ensure the proper settings are being applied, they need more information:
- Why does this Microsoft Team exist?
- Will it have sensitive data?
- Is it for a project?
- Will it require guest users?
Once again, to gain critical context, IT is forced to go through a time-consuming. Manual process — in this case, communicating with the requestor and the business owner. An additional challenge is that once the workspace is provisioned. The Owner of that workspace can change the settings at any time in its lifecycle.
This process can eat into your budget and bandwidth. A survey of IT professionals conducted by the AIIM (Association for Information and Image Management). And commissioned, found that 63 percent of respondents spent 4 to 8 hours per week performing routine. SharePoint governance tasks such as provisioning, changing permissions, and revising site settings.
Though file sharing in Microsoft Teams is powerful. It can be confusing for some users and may end up becoming a burden. Files are can get scattered everywhere, permissions can get neglected, and data security can become compromised. To avoid all of this, here are some of the basic file and document. Practices every Microsoft Teams user should know about with SharePoint development.
Share files with the proper permissions
Share files with no permissions configured
As the owner of a document, you need to ensure its security. A crucial part of this is providing the correct permissions to whom you are sharing it with. To quickly share files in Microsoft Teams, go to the chat window. And click on the paper clip icon to add your files. There should also be an option to share a file from OneDrive without leaving Microsoft Teams.
In the same chat window you can configure the permissions of the file you’re sharing. You can even choose between allowing editing access and viewing access with SharePoint development. And there are various sharing options you can choose from.
Directly create a document in the Microsoft Teams app
Create and share documents separately that might cause versioning issues
One of the common mistakes some users make when working. On a document is having multiple versions of a file at once with SharePoint development. Hence, changes are not tracked in real-time and collaboration becomes a challenge. To address this issue, Microsoft Teams lets you create new documents or work on existing ones from right inside the app. This includes Word, PowerPoint, Excel, OneNote, and more.
To proceed, go to the Teams tab from the main menu (left side of the app window) and find the group or Team you want to work with, then go to the Files tab.