In Office 365 you have the option to add a partner to your Office 365 tenant. In this article I explain what the partner sees and what can they do.
In your Office 365 portal you see ‘Partner relationships’, here you will find a list of Microsoft Partners that have delegated access to your tenant. The Microsoft partner can ask for delegated access to your tenant, you cannot invite the partner yourself.
We are rolling out Office 365 at my current assignment. Within this project we want to automate as much as possible to avoid human error and reoccurring tasks. We already used a lot of PowerShell for our current SharePoint farm, so the most obvious thing was to look at PowerShell for automating those tasks. In this article I will take you with me on the journey that we took.
We choose Azure Automation for a few reasons. We started with a few PowerShell scripts from my workstation to see what we could automate and tried to set the default usage location of the user. This is something every user needs before a license can be assigned. We wanted to run this script every 3 hours after the Active Directory synchronization. Our first thought was we can use the Windows task scheduler just like ADSync (We started a year ago with this). The problem with using a task scheduler is that we need to authenticate to Office 365 and we cannot run this script with the current credentials. An option is to just enter the username and password into the script. This is a big NO. Another option was to save the encrypted password and use that one in our script, this one I could not get to work.
Some time back we updated Azure AD Connect at a customer to the latest version. The update itself was an easy one, just next, next finish like they described on the Azure site. But what we found is that the sync engine itself was completely different. The previous version had a Windows timer job as it schedule and ran every 3 hour. You also where able to run that command (DirSyncClientCmd) with a parameter (initial or delta) to run a new or delta sync.
I’m currently working in a large enterprise where we have a dedicated team of SharePoint administrators. This team is responsible for the current on-premises SharePoint environment. The way we give this team control over the whole environment is with the option ‘User Policy’ within the web application. Here we give the whole team administrator rights for the web application. This way we do not have to assign rights to every single site collection.
From the beginning of SharePoint Online we have the option to share a site or document with an external user. When you use this feature the recipient need to have a Microsoft Account to login your SharePoint environment. Because this can be very confusion for the user, Microsoft is working on a Business 2 Business connection within Azure AD. With this connection you can share that same site or document with a user from another Azure AD tenant.
This weekend we did a migration between 2 tenant and with this migration we noticed that the URL for OneDrive 4 Business was changed on the old tenant after we changed the domain name for all the users.
This means when you change the UPN of a user not only the primary email address is changed but also the user profile in SharePoint Online.
I did a test with another tenant to see how long it takes for the URL to change; this gives an indication about the profile update time.
This week I did my first presentation for DIWUG witch was a great success. The presentation can be viewed below.
20160128 - Diwug Azure AD en SharePoint (Online), en hoe doe je dat precies—Arjan Cornelissen
Microsoft has released a new framework for developing an awesome front-end called Office UI Fabric. So the big question is why did Microsoft created this framework? We already have a ton of different frameworks for front-end development like Bootstrap, Semantic UI, 960 Grid System and many more.
The short answer is that we did not have a framework for creating Office or SharePoint add-ins that integrates with the looks of Office applications.
Since the introduction of SharePoint 2013 and Office 2013 we as developers have a new option to integrate our applications in SharePoint and Office. The add-in model is in basics just a web application that integrates in SharePoint and Office. Until a few months ago we could not make our add-in look like a part of Office. Andrew Connell wrote a great blog in February of 2015 that we needed guidelines for integrating in Office. The answer to this is the Office UI Fabric that is posted on GitHub.
There are a number of blogs already written about how to get the Geolocation column on your SharePoint site, but a lot of sites use the wrong syntax for the field XML. Even the MSDN site for adding the geolocation column to your site is incomplete.
The correct XML to use is:
The important part here is the addition of the Name property in the field definition. The complete script to add it to your site is:
After reading this blog of Matthias Einig about using Azure Analytics for your Office 365 portal. I tried this on an clients SharePoint 2013 farm. But I didn’t want to create an app to deploy the JavaScript so I created an Console app to deploy this to the specific site collection.
I first wanted to create a PowerShell script, but that does not work with our farm because of the discovering of the ADFS settings. I created an issue for this on GitHub (https://github.com/OfficeDev/PnP/issues/1118). So for the console app I used the OfficeDevPnP core Nuget package (https://www.nuget.org/profiles/officedevpnp).