Microsoft Purview DLP Extends to Microsoft 365 Copilot

on
As organizations increasingly adopt Microsoft 365 Copilot to enhance productivity and collaboration, ensuring the security of corporate data becomes more and more important. Microsoft Purview Data Loss Prevention (DLP) offers a robust solution to safeguard sensitive information. Purview's new and upcoming DLP capabilities can soon help secure your organization's use of Copilot even better. Microsoft Purview Data Loss Prevention (DLP) is expanding its capabilities to support Microsoft 365 Copilot. This enhancement will allow DLP policies to identify sensitive documents using sensitivity labels and exclude them from processing in Microsoft 365 Copilot Business Chat. The feature will be available for customers who already have E5 (or equivalent) licenses together with copilot licenses. Information protection admins can then create policies that will include Microsoft Copilot in addition to all of the existing services. The preview started in late November, and it should be availab...

Missing Meet URL for users of Lync Hoster Pack v2

on
The company I work for deployed Lync Hoster Pack v2 in the fall of 2013. At first, all things seemed fine, but after a while we received incident tickets regarding users who did not get the meet url published when creating a new meeting.

It has been a long road tring to find the root cause of this issue, especially since we at first saw no difference between the users we created where it worked, and users where it did not work. All users were deployed through the Citrix Cortex service for provisioning.

All users were provisioned correctly with Domainmap, TenentID and ObjectID. And if we moved users from one place to another it started working again.

It all turned out to be a rights issue in Active Directory. The root OU had it's correct settings, but when we deployed several resellers through the Cortex service, these reseller OU's did not inherit the rights from the parent OU. Applying the correct rights to all the sub OU's in the tree fixed the issue for all customers.

Here's a quick script to set the correct rights for hosting on all OU's in a tree:

Import-Module activedirectory
Import-Module lync
$counting = 0
$moreISH = Get-ADOrganizationalUnit -LDAPFilter '(name=*)' -SearchBase `
'ou=reseller,ou=hosting,dc=domain,dc=net'| select DistinguishedName
foreach ($ou in $moreISH){
Grant-CsOuPermission -OU $ou.DistinguishedName -Verbose -ObjectType user
$counting ++
}
Write-Host "Set rights on $counting OU's" -ForegroundColor Green

The commands above must be run a computer where the Active Directory and the Lync module is available.

These are the changes made by the command http://technet.microsoft.com/en-us/library/hh849655(v=ocs.14).aspx