Nov 05 2019 02:05 PM
Nov 05 2019 02:05 PM
Hey all, anyone have and advice on what is the PROPER way to take a Sharepoint Online site that was created from a MS Teams team and opening it to a Public (RO) site? We found multiple ways, but just want to know what is the best practice. Thanks!
Nov 05 2019 03:13 PM
Nov 05 2019 03:20 PM
@Juan Carlos González MartínPublic=viewable by anyone. Does not have to be inside our org. Does not require login. If we used Conversations on the SPO site though, would want people to login before they could make a comment.
Nov 05 2019 05:30 PMSolution
@Jleebiker SharePoint Online does not support public websites. Everyone has to either be a member of your organization or be explicitly invited to the site.
Nov 06 2019 08:50 PM
Nov 06 2019 10:51 PM
Nov 07 2019 02:27 PM
Nov 07 2019 02:37 PM
Thanks @Chris Webb. I've asked around in a few places and what I get overwhelmingly is "It isn't supported. Forget it." Thanks for being a beacon of hope.
One of our use-cases is preemployment onboarding so your workaround is enticing. The problem is when we have webparts that have content that require a login and are not just simple pages we can grant anon access to.
Quite frankly, I expected better when I went digging for this. I was told numerous times to forget it. I asked why and was told "Because Microsoft doesn't support it." Cmon folks, be better than this. Push the status quo. Ask the question as to Why. After all Satya even said this week that his goal is to democratize access to data. Why not make it easy for people to access info no matter how they are creating it. Why have the barrier?
Yes, this can be done with SP on-prem, but what about orgs that do not have an on-prem server? What about making it easy and fluid for orgs to interact with people outside their tenant? Isn't that what Microsoft wants to do?
Nov 07 2019 02:40 PM
Nov 07 2019 02:46 PM
Nov 11 2019 07:18 AM - edited Nov 11 2019 07:21 AM
@Jleebiker Microsoft does make it easy to interact with people outside of the tenant, as external guests. Unfortunately, you want public sites... but you are paying for a *service* and it's just not something that is offered anymore.
With public sites, you'd be asking Microsoft to support the infrastructure/load of N number of users to Office 365... essentially for free. That really isn't a good business model. Second, SharePoint was never the best/easiest public facing platform. There are better web hosting providers, that make it easier to consume web content.
My personal recommendation would to get up a site on a public hosting service such as GoDaddy/WordPress to share this kind of content. Anonymous sharing links could work, if your sharing content such as files and don't need full fledged SharePoint features.
Nov 11 2019 07:24 AM
See, now THAT's the kind of answer I was looking for. Thanks @Beau Cameron for the WHY behind the reason.
Would it be safe to assume it could still be used as a B2B solution where we know the people wanting access? If it is a capacity issue, do you have any guidelines as to when a site should be considered a candidate for putting on a dedicated B2C type solution? Thanks for the dialogue!
Nov 11 2019 07:38 AM - edited Nov 11 2019 08:11 AM
@Jleebiker Well the discussion really depends on the definition of B2C. Not only for your company, but in the eyes of Microsoft Tenants. In the outside world, we think of B2C as essentially public.
In the Microsoft Tenant world, B2C carries some of the same methodologies of the ability for non-organizational people to gain access to your content...However, Office 365 is a licensed service, meaning users who access content within your environment need licenses (either granted by you, or granted via External User flow).
I personally, do not like the idea of anonymous sharing links and in fact recommend disabling anonymous sharing links. Which makes my decision quite easy... if I have something that can be accessed by anyone, I stick it in a public site. I've built integrations with WordPress to copy/sync documents to a public word press site for this exact scenario. It benefits you for a couple of reasons.
1. You don't have to worry about access to your company's Office 365 Environment. If you have external sharing on, and anonymous links... without more IT oversight (though external perms can be managed at the site level), implementation of S&C services likes DLP, you are opening up the possibility of allowing your users to share internal content... that they shouldn't.
2. Being on a public platform allows you to create a nice looking web site, with your branding, corporate messaging and streamlined permissions management. SharePoint has never been a leader in WCM.
Nov 11 2019 08:17 AM
Oct 05 2020 04:48 PM
@Jleebiker I think I just figured this out! Here are the steps:
1. Go to the site page
2. Select Settings (tool icon) in the top right corner of the site
3. Select 'Site Information'
4. Scroll down until you see 'Privacy Settings' and change from Private to Public, or vice versa
Hope this helps people!
Oct 20 2021 02:36 AM