Hi Mch,

Thank you for your information. I have reproduced the situation. It is like you described. I suggest sending a feedback on the Office 365 website (mymfe.microsoft.com/.../Feedback.aspx). The related team will further confirm the issue.

Best Regards,

Monica

Monica,

Thanks, but is the feedback form really the best way to address this?

I had already filed a service request which I'll post here in the hope someone picks up on it:

1154167046

What you are experiencing is typical with the Public Website as it was not designed to house subsites. Your Team Site is supposed to fulfill this purpose. While this is technically another site collection and does have the ability to house subsites, the specialized design of the Public Website separates it from any typical site collection you would create through Tenant Administration.

With the Public Website, the idea is to create a hierarchy through pages that sit atop the site collection and maintain the anonymous access you’re referring to. When you navigate to https://PUBLICWEBSITEURL/_layouts/settings.aspx, you enter into the Site Settings for your Public Website. Within, the Quick Launch will show you Pages, Images, Documents and Templates. You’d want to keep your focus on these options. For example, in Pages, you have a Pages control tab that reveals itself and allows you to create a New Page which you can also edit from here. All this within the same, anonymous-controlled site collection.

Patrick,

I appreciate your input, but it doesn't really address my question. Whether or not it's intentional, the fact is you CAN create sub sites under the public site but the anonymous access permission isn't applied to every element of the sub site. This is clearly in conflict with normal Sharepoint protocols and needs to be addressed.

What a lot of people don't realize is that Sharepoint Online is nothing new-OLSB included the first version of it and some of us got used to being able to deploy SP applications on a public web site. O365 has more sophisticated templates than OLSB but lacks the intuitive tools to deploy them on a public site. This is really what I'm asking for.

mch,

At this juncture, I encourage you to create a new service request using the following link: portal.microsoftonline.com/.../NewSignupServiceRequest.aspx.

Although I see you refer to a prior service request, please log a new one using this method to improve accountability and assure accuracy in process. The appropriate team is going to need to research the intended functionality of this pattern as this is still in the Beta stage and some features will not be present or properly functional until GA. Some features that appear to be erroneous are sometimes intentional based on how it affects other aspects of the system. It could turn out that this feature is required to ensure more important elements of the system operate properly. If we do not see there is any notable precedent to this behavior, we may need to submit a Hosting request to either review the current behavior for anything in error or note in detail why the requested functionality cannot be met.

Please post in this forum the service request number you are assigned once it has been created. Once it has been, please refrain from discussion of the incident in the forum and allow our Moderators to close this post to funnel any further work into the service request itself.

mch,

I haven't seen any note of your creation of a new service request. Was this done?

it does look like Monica has givin you the correct information. For additional help please create a case using the following link: portal.microsoftonline.com/.../NewSignupServiceRequest.aspx

Thanks.

SR is 1156478233