Can't add a calendar to Office365 Website
I just created a trial account to test Office365 for my non-profit. I don't have most of the lists (now called Apps) available, such as Calendar or Links. Someone suggested activating the "Team Collaboration Lists" feature, which lead me to this post because I couldn't see Site Collection Features either.

I have four site collections that were created for me, one called "Website", that has a URL like this:

and three site collections, including


I mistakenly thought these were the same site collection. I have been populating my Website, and everything seems OK except for not having these list options. So, I tried a suggestion on the Office 365 Community site.

"https://{mysite}" resolves correctly, and "Team Collaboration Lists" feature is active, and I CAN see Links, Calendar, Tasks, etc.

"https://{mysite}" gives me a 404 error, with http or with https. Plus, I can only see a handful of available Apps on the Add an App page, such as Custom List or Document Library.

Why are the App choices for my "Website" site collection so limited? Is this standard for Office 365 Enterprise E3 for nonprofits? If so, why do I have the capability on my team site, "https://{mysite}.sharepoint.
January 31st, 2014 2:59am

Team site meant for collaboration thats why you have all the option but publich site is more for publishing stuff, like your content etc.

here is article which give you more about public site.

Get started with the Public Website

and here is another for limitation:

SharePoint Online: software boundaries and limits

here is info about team site

Start using your team site

Free Windows Admin Tool Kit Click here and download it now
January 31st, 2014 5:50am

Hi Christopher,

When you first open your Office 365 Admin page, you'll see the 4 sites you describe.

http://{mysite} is as you've seen the public facing internet site. This is meant to be branded and used as a publishing internet site. Usually these are edited by only a couple of people and consumed by many.

As a result, this website does not have a lot of apps installed or configured because it's basically just a brochure web site.

The other site collections under the "site Collections" heading are what are considered your 'internal' sites where the bulk of collaboration would happen.

https://{mysite} is where all of your user profiles are displayed. Thats the site you see when you click on about me on your name drop down in the top right.

https://{mysite} is the main landing page for your SharePoint site. if you're users go directly to and use the credntials you set up for them, they willbe directed to this page afterwards. This site collection and any you create in the /Sites managed path afterwards is where you do all the collaboration goodness and where the use of Apps makes most sense.

Finally you'll see https://{mysite}, this is the pre-built search portal for your site collection which you shouldn't need to do much to.

If you use the New button on the top of the Site Collections mangement page, generally you'll only be able to create new Private Site Collections. These will all be created under the url https://{mysite}{new site collection here}

Hope that helps explains things a bit.


January 31st, 2014 7:38pm

That does explain the functionality, Paul, but it doesn't answer my real question: WHY?

I can understand making the public website a blank template. But every version of SharePoint gives you the ability to ADD to a template, if you know what you are doing. Is Microsoft seriously arguing that a public-facing web site doesn't need a CALENDAR? Or LINKS?

I mean, my biggest complaint about Microsoft is their insistence on tying people's hands. Sure, make it easy for the novice to get going. Give them a dumbed-down version so they are not overwhelmed. I TOTALLY get that. But if you actually KNOW what you are doing, why are you prevented from using tools that are available elsewhere?

If I build a public site for a church, or a non-profit group, or any kind of group or club whatsoever, the number one requirement is a CALENDAR of events. That's not a collaboration tool, that's basic functionality!  here are my three options for a SharePoint site:

  1. Use the out of the box Calendar.
  2. Create a Custom List and add an Event Content Type and a Calendar View.
  3. Find a third-party tool that basically does No. 2.

So, Microsoft is saying, 2 or 3 is fine, but 1 isn't? I would really, really like to hear a Microsoft person justify this. As a long-time developer, I have spent most of my career working with Microsoft products. It is really frustrating to have to find work-arounds for what I consider unnecessary design decisions.

Finally, is this the same for every version of Office 365? If I want to have a public-facing website that uses SharePoint, am I going to be similarly crippled regardless of which version I sign up for?

Free Windows Admin Tool Kit Click here and download it now
February 3rd, 2014 7:03am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics