Last weekend I visited SharePoint Saturday in Brussel Belgium. This was my fourth time here in Belgium and again a great one. The day was setup up 6 sessions of 50 minutes and a lunch break of 1.5 hours with a 30 minute.
We started at 9 with a welcome from the BIWUG team and the first session started short after that. I started with some developer sessions.
Get Typing with TypeScript I started the day with a session from David Opdendries (@sharepointdavid)
Last week I had the privilege to attent Microsoft Ignite in Atlanta. This week was full of news, sessions and a lot of walking. Besides the sessions, this year the expo hall was large, I have spend a lot of time at the expo talking to venders, partners and Microsoft.
I have created a PDF from all my notes. On a few notes I have references to slides, the slides should be come available on https://myignite.
This week I will attend Microsoft Ignites 2016 conference in Atlanta. To make it easier for everyone to follow me I have created a OneNote that I will use to share my notes.
You can find that OneNote here: https://arjansp.nl/Ignite2016Notes
A few weeks ago it was the time of the year that the signing certificate of ADFS was expiring. Last year it took us by surprise because the ADFS team did not notify us and we did not put it in our agenda’s that the certificate would expire. So last year we had a lot of people complaining that SharePoint 2013 was not available anymore.
This year we had it in our agenda’s that the certificate would roll over, so we were prepared for a roll over and had contact with the ADFS team and made an arrangement to roll over the certificate.
Last week I got an email from a coworker that Microsoft has created a score website (https://securescore.office.com/) for Office 365 tenants. This website measures the security of your Office 365 tenant. By default the score of your Office 365 tenant is very low, I got on my personal tenant a score of 29 out of 243 and on one of my customers also got 29 out of 243.
What does it rank This website ranks about 60 settings within your tenant divided by three categories
I’m part of the Microsoft Heroes at Sogeti and this week we had an evening event about DevOps where I did a talk about the operations part of DevOps for Office 365.
At my current customer we are preparing Office 365 for deployment to every employee in the Netherlands. So far we had moved 1000 employees of one operating company and we are now working to get the rest of the Dutch working companies to Office 365.
As a follow up on my post from last week I wanted to add some extra data in the terms. This is not possible with the default CSV import that SharePoint has. I mentioned in my previous post that Office Dev PnP has also an option to import terms. And with that option we can add a lot more than only the term itself.
What commands do we have? We have a 2 options here to add term to Office 365.
This week I was working with the term store and had to create and import a big chuck of data in the term store. We all know that we have multiple options here
Just enter them one by one in the browser (great for a few entries) Use the csv import Use CSOM Use Office Dev PnP PowerShell This post will address the csv import.
Getting started with the csv For the csv import we have a sample that can be downloaded from the term store (http://-admin.
This week I had a customer that has some data in their on-premises Active directory that we needed to use for a custom application in SharePoint Online. This data was placed in the ExtensionAttribute field of the user. With the latest version of Azure AD Connect we have the option to select attributes to sync to Azure Active Directory and that is what the customer did. https://azure.microsoft.com/en-us/documentation/articles/active-directory-aadconnectsync-feature-directory-extensions/
This screenshot has selected division and employeeID, but in the complete list of available attributes there are also the ExtensionAttributes.
Last week Microsoft has send an email that on august 15th 2016 the Azure AD token-signing certificate would roll over and that I had some applications that is using this token-signing certificates. The list of applications contains all of them, this was not very useful.
Luckily there is a short step-by-step instruction with a link to a complete manual (https://azure.microsoft.com/en-us/documentation/articles/active-directory-signing-key-rollover)
Because I manage a few Azure Active directories like many developers, this was going to give me some work.