DRAG DROP
You are the Office 365 administrator for your company. The company has multiple Microsoft SharePoint Online
sites that are shared with external users. Individual documents have also been shared from other Microsoft
SharePoint Online sites.
The company recently ended collaboration with a vendor named Contoso, Ltd.
You need to revoke all sharing with external users who log in with contoso.com accounts without affecting
sharing with other vendors.
Which three actions should you perform in sequence? To answer, move the appropriate actions from the list of
actions to the answer area and arrange them in the correct order.
Select and Place:
Explanation:
Contoso users have access to multiple shared files and multiple shared sites throughout the SharePoint site
structure.
The easiest way to remove Contoso users’ access to all the shared resources is to remove the Contoso users
at the top level of the SharePoint structure, the Tenant.
The Remove-SPOExternalUser PowerShell cmdlet is used to remove a collection of external users from the
tenancy’s folder.
To run the Remove-SPOExternalUser cmdlet, we first need to open the SharePoint Online management Shell
(Step 1) and connect to the SharePoint Online tenant by running the Connect-SPOService cmdlet (Step 2). We
can then run the Remove-SPOExternalUser cmdlet as in Step 3.https://technet.microsoft.com/en-gb/library/jj730437.aspx
I disagree with #1. Windows PowerShell doesn’t know about SPO cmdlets, so it has to be Open the SharePoint Online Management Shell
The connect-SPOService will however load in cmdlets specific to SPO though, right? 🙂
The solution should include one more command that is not among the alternatives;
$ExtUsers = Get-SPOExternalUser -filter ‘@contoso.com’
to get the unique IDs needed for
Remove-SPOExternalUser -UniqueIDs @($ExtUser.UniqueId).
(https://support.microsoft.com/en-us/help/3026385/how-to-remove-users-from-sharepoint-online)
CompatibilityLevel 14 => SharePoint 2010 Products
I would answer :
1 – Open SharePoint Online Management Shell (otherwise the cmdlet Connect-SpoSite is unknown )
2 – Run the Connect-SPOSite -URL https://contoso-admin.sharepoint.com …
3 – NewSpoSite with -CompatibilityLevel14 (because there are legacy application perhaps in SharePoint 2010)
I agree that 1 and 2 are correct. Disagree with number 3, -CompatabilityLevel 14 will make it a SharePoint 2010 site, while 15 will be a SharePoint 2013 compatible site. If left out, it will make it the current level, which at this time would be SharePoint 2016. I believe option 3 in the answer is correct