Pascal Bonheur

One error I’m often asked about when activating the multi tenant on SharePoint 2010 : if you want to enable tenant admin to create site collection, you may see this error:

This is most of the time due to the fact that the self service creation is not activate at the Web App level:

Once this is On, the site collection creation should work….

Office 365 allows you to convert an “Intranet” sharepoint site to an “Extranet” sharepoint site meaning that you can invite external users to your site.

Notice that you have a Share Site option in the Site actions:

If you select that you will see that you cannot share will external users:

So we need to activate some features to make it work…

Here are the steps to do that:

1. In the administration, go to Site Collection admin, select the site collection and then click on Manage Share By Mail:

2. Choose Allow

3. Go in the Site Collection features and activate the “External user invitation” feature:

4. Go back in the Share Site option in site settings:

5. Invite an  e mail:

and here you are…

If you have read one of my previous post about deploying Web Part to Office 365 you may wonder if Web Part are the only custom development that can be deployed in Office 365… The answer is no….

Let’s have  a look at deploying an event receiver.

Just create an empty project :

choose SandBox in order to deploy to Office 365… if you don’t do that it won’t deploy….

Note that in the URL, I have my SharePoint Online address in the screenshot but it doesn’t seem to work when you deploy. Instead you have to do it localy (ensure that User Code service is started !):

Create a new Event Receiver

enter some code…

public override void ItemAdding(SPItemEventProperties properties)
      {
          properties.AfterProperties["Title"] = "Changed by event receiver at" + DateTime.Now.TimeOfDay.ToString();
          base.ItemAdding(properties);
      }

Then build the .wsp.

Last step, go to the solution part in your SharePoint Online :

Then activate the solution

Then create a new item in a list based on the template that you have choosen when you created the event receiver and watch for the change

:

If you create a public Web Site with Office 365, you may have noticed that there is no Site Settings in the Site Action menu even if you have administrative rights:

In order to go in the settings, you can either type the URL _layouts/settings.aspx and it will work:

or open the site with SharePoint designer:

Interesting shortcut in Office 365 to quickly add users to a site:

and specify the users…

Interestingly, when you provision a SharePoint Site, a content type Hub is automatically created and configured for you:

If you want to have automatic update, you just have to check the checkbox.

Now let’s have a look on what happen if you create a new site collection:

Then enter the parameters:

Interesting point to note, you can specify quota and also resources and you will see what’s left before you proceed:

then in this newly created site collection, have a look at the content type hub settings:

…so it is pointing to the main Content type hub.

Let’s try to do a change in one of the content type like adding a colon to a task: (TOTO in my screenshot):

Then publish the content type:

Then … you have to wait for the timer job to do the Sync (not sure if this is the 15 mn as on premise…) and you can see that the task content type has been updated in the site collection:

Un document tres pertinent pour monter un plan d’adoption pour SharePoint:

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=94ee6518-75f7-47be-b4c1-0d6ec1248486

Let’s create a web site that is publically available on Office 365…

From the administration, go in the SharePoint admin and create a public web site collection:

Enter the Web Site information. As you can see, you can only choose 1 address which mean one Public Web Site:

Then wait for the site to be provisioned :

Notice that the New Public Web Site option is now greyed out…

Navigate to you site :

If you try to install SharePoint 2010 and do some BI on a SQL instance that host a cube and a reporting services, here are some interesting point you may want to note:

• For the SPN of the cube, use the port of the instance and NOT THE NAME as specified in Microsoft documentation…
• Create a static port instance for the Analysis Services instance otherwise the port will change every time…
• You can use the DNS name in the SPN for the Analysis services
• You cannot !! use the DNS name for the reporting services. Instead use the name of the server

Hope this helps…