This weekend I had the privilege to speak at SharePoint Saturday in Leicester. Here I did a session on Protecting your data in office 365. I talked about how we did security before the cloud and what Microsoft provides to keep your data safe in Office 365. I showed Multifactor authentication with Conditional Access, disabling legacy authentication, Privileged Identity Management, Identity Secure Score and Password less Authentication.
See my deck below
It was that time of the year again to visit Belgium for their SharePoint Saturday. An excellent day organized by BIWUG.
This year was a tribute to an amazing SharePoint teacher who passed away too soon, Patrick Tisseghem. I did not know him but heard and read about him, I only was working 1 year with SharePoint when he passed away. During the day there were videos and photos about the things he did for the community.
In the week of September 24th, Microsoft held their biggest tech event of the year and I had the privilege to be there again. This post will give you a summary of my journey thru this week.
The official conference starts on Monday but on Sunday evening I got invited to the welcome party of Microsoft Netherlands to meet all Dutch participant, get to know the others and meet all we already know. This is a great way to start the conference.
Some time ago I got the question if it was possible to start using AAD Connect while some of the users are already in Office 365 with a cloud account without losing their content and access. So this was a first that I had this question and found myself searching on the internet and found an article from Microsoft that this was possible. https://docs.microsoft.com/en-us/azure/active-directory/connect/active-directory-aadconnect-existing-tenant
This article describes that you can start syncing an on-premises AD with Azure AD when you already have users in Azure AD. AAD Connect then tries to connect the on-premises user to the cloud user. There are two types of matching Microsoft does, Hard match and Soft match. A hard match is done on the “SourceAnchor/ImmutableId” in Azure AD, and a soft match is on the combination “UserPrincipalName” and “Proxyaddresses”, and then only the primary email address is used.
This week I needed to remove all users from a tenant that was created by Microsoft because their domain was not yet added to our tenant and the users started to use Power BI with there email address. So I needed to become the owner and remove everything to add this domain to ours. Because of this new tenant, I got some tips in the admin portal because of first use. Here I got this tip when I opened one user to remove it.
This morning I had the ability to deliver a session at SharePoint Saturday in the Netherlands. The session is about first line workers and what Office 365 has to offer them. See below a really great sketchnote that Luise (@LuiseFreese) made.
[https://x.com/LuiseFreese/status/1012977243805704198](Twitter post)
The complete presentation can be viewed on SlideShare [slideshare id=103742312&doc=20180630-spsnlusingoffice365foryourfirstlineworkers-180630111437]
Today I saw a notification in the Office 365 Portal about the correct sizing of Shared Mailboxes.
It seems that Microsoft is creating Shared and resource mailboxes with a max limit of 100GB. As the documentation states these mailboxes can only have a size of 50GB and when you need more space you need to assign an Exchange Plan 2 license to that mailbox to get 100GB of space for that mailbox. https://technet.microsoft.com/en-us/library/exchange-online-limits.aspx#StorageLimits This change of the size limit will be applied on July 30th, 2018. See this roadmap item for more details https://products.office.com/nl-NL/business/office-365-roadmap?filters=&featureid=31391
I have noticed that not every domain register can add every DNS record that is needed for Office 365. This leaves you with two options, move your domain to another register or host your DNS records somewhere else. To host your DNS records in Azure DNS, you need to be able to update your NS records at your domain register. If that is not an option, you need to move the domain to another register.
In this post, I want to take you with me how you can use app credentials in an Azure Automation script to connect to SharePoint Online. Many PowerShell scripts use a username and password, but these are less secure than using an app credential and can also be used to login to SharePoint Online in the browser. By default, connecting to SharePoint uses basic authentication and many companies are on route to disable this to make use of conditional Access and MFA.
It was time again for the European Collaboration Summit. After the success of last year, I attended again. This time it was a bit closer to home in Mainz.
We started on Tuesday with a keynote from Dan Holme (@DanHolme) with a recap of the SharePoint Conference in Las Vegas from last week. The take a way’s for me were
After the keynote, I went to the session “Enabling the protection, detection, and response to cyber-threats” of Martina Grom (@magrom)