External Sharing in SharePoint and OneDrive is changing: What You Need to Know

In an ongoing effort to create a more secure environment by default, Microsoft is introducing an important security update that will affect how external users access content shared through SharePoint and OneDrive. Starting July 1, 2025, any links shared with external users before your organization enabled Microsoft Entra B2B integration will no longer work. This change applies to all organizations that have already enabled or will enable SharePoint and OneDrive integration with Microsoft Entra B2B (Most organizations I have looked into so far). External users trying to use old links will see an error message saying the organization has updated its guest access settings. To regain access, the content must be reshared. Highlights of how the change affects organizations who have enabled B2B: All external sharing will require guest registration. External users must be added as guests in your Microsoft Entra directory. Access will be managed through Microsoft Entra B2B Invitation Manager. T...

Missing Meet URL for users of Lync Hoster Pack v2

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