Group-connected SharePoint site was restored after the group was deleted
Hello, I'm not sure if this post is a topic for SharePoint or Office Groups. I know a deleted Office group can be restored for 30 days. The SharePoint site for 93 days via the SharePoint recycle bin. Now we have a situation that we restored a site after 70 days, and yes, the connected group was already deleted. I found no description from Microsoft about this case. We saw the site has issues related to the missing group. What are the known or recommended steps in such cases? Can we recreate a new, empty group for the SharePoint site? In a normal case it's possible to connect a new group to an existing, not group-connected SharePoint team site. But this option is not available for a restored team site. Thanks for some information.
Office 365 groups vs office 365 security groups
Hi Experts, Like many I would like to do away with Security groups in favour of Office 365 groups where possible. I did come across this blog https://threewill.com/office-365-groups-vs-azure-ad-security-groups/ which details it is not the best idea. The ideal situation would be that an Office 365 group, lets say Team 1 can manage multiple sites. For example, they would have a "public facing" sharepoint site where they are publishing information to the business and a SharePoint site (part of their Microsoft Teams site) where Team 1 would internally collaborative. Team 1 and Team 2 are part of Department A. There is a business facing/publishing site for Department A that Team 1 and 2 are contributors, also the Department A has a Microsoft Team site for internal collaboration. Is this best practice to use as Office 365 groups? The https://threewill.com/office-365-groups-vs-azure-ad-security-groups/ and https://docs.microsoft.com/en-us/office365/admin/create-groups/compare-groups?view=o365-worldwide#:~:targetText=Office%20365%20groups%20are%20used,granting%20access%20to%20SharePoint%20resources. suggests otherwise. I'm guessing Departments, Divisions and Teams with people should continue to have an office 365 security group and Projects, Committees or working groups should have and Office 365 group. I have a few questions surrounding office 365 groups vs security groups (some answers to also help people!) Office 365 Group Office 365 Security Group Business Owners can manage Yes No Devices can be added No Yes Can Searchable by the organization Yes No Creates mailbox, team site and calendar Yes No Ability to nest same group type within ? ? Can set to expire Yes No Can associate with Communication SharePoint Sites No Yes Can associate with Team SharePoint sites Yes No Can be the owner multiple sites ? Yes Dynamically add members Yes Yes Add external members Yes ? Thanks!
Manage external users for "SharePoint" & "Office 365" groups when creating MS Teams
I have create a new MS Teams, and i set it as private, as follow:- which have created a new sharepoint site, which have the following external sharing settings:- and also have created a new Office 365 group, which does not allow external sharing as follow:- now i have the following questions:- 1) i have shared the sharepoint site with an external user, and the user can access the sharepoint site and upload documents. but i am not sure what the user can not do, since he was not added inside the Office 365 group? 2) as i know MS teams allow chatting through its desktop application, but seems the MS Teams itself does not have an external sharing settings.. so if i share the sharepoint site with an external user, will this user be able to chat with other members inside the MS Teams? the confusion is that MS Teams itself does not have an external sharing setting + does not have a module to add users to it... Can anyone advice on my above 2 questions? Thanks
Office 365 Groups and Outlook
Are Office 365 groups meant to show up in my normal Outlook client? They show up online but not in my standard Outlook. I've read that they aren't meant to show if the group was set up on Teams, but this group was set up on SharePoint as a a 'Team Site', I then chose to go and add this on Teams after. What I do find weird is that I can add the calendar of the group to my 'Shared Calendar' options on my Outlook, but instead of showing any of the events that are in the calendar online, it shows all of the events in all of the admin's calendar (there are three of us) and blanks them out as Busy. Is this normal behaviour? I was hoping to just show the events that are in the calendar online. Group Calendar Outlook Online Outlook CalendarProgrammatically create and Add Owners and Members to O365 Group, no emails are sent
I'm using the code found in OfficeDevPnP.Core to create a new UnifiedGroup. UnifiedGroupsUtitlity.CreateUnifiedGroup. My code is below. UnifiedGroupsUtility.CreateUnifiedGroup("CSOM Site Creation", "My Site Created in Code, CSOM, accessToken, groupLogo: null, owners: owners.ToArray(), members: members.ToArray(), isPrivate: true, createTeam: false); When I'm using this code, none of the Owners or members get's an email saying they have joined the group, like they do if I add them manually to a group. Do I have to write that part of the code to send the emails, or is there another method I can use that's already out there to send the same template that Microsoft sends? There are two emails sent (if MS Teams included), when adding a person manually. One to say the person is added to the group from: The site on behalf of me. One to say the person is added to the MS Teams. From: noreply@email.teams.microsoft.com It these emails I wish to replicate when adding a user to Group/Team.
Group Connected Site Taxonomy Feature not activated
Hi, If you created a SharePoint Team Site that is connected to a Office 365 Group the hidden taxonomy Feature is not activated. So you can`t create a managed metadata field. Does any body know is there a reason for that or is it supported to activate the Feature? I successfully activated the Feature via PnP but it is a bit strange that it is not activated by default.Group Connected Site Taxonomy Feature not activated
Hi, If you created a SharePoint Team Site that is connected to a Office 365 Group the hidden taxonomy Feature is not activated. So you can`t create a managed metadata field. Does any body know is there a reason for that or is it supported to activate the Feature? I successfully activated the Feature via PnP but it is a bit strange that it is not activated by default.Office 365 Group Expiration and SharePoint Group Connected sites
We have a growing number of self-provisioned Office 365 groups. We also have a list of admin provisioned sites. We want to manage the growth of the self-provisioned using Office 365 Group Expiration Policies. What I can't get clear is, will these Group Expiration Policies apply to both self-provisioned and admin provisioned sites the same way? Or can we exclude sites we've created from expiring?Office 365 Group Expiration and SharePoint Group Connected sites
We have a growing number of self-provisioned Office 365 groups. We also have a list of admin provisioned sites. We want to manage the growth of the self-provisioned using Office 365 Group Expiration Policies. What I can't get clear is, will these Group Expiration Policies apply to both self-provisioned and admin provisioned sites the same way? Or can we exclude sites we've created from expiring?
Saving to SharePoint Online from Desktop
So I have a user who is a member of a Office 365 group. He wants to know how to save directly to the document library within the Group. Demonstrating the save to Sites to him we notice that his directories are not available and the message indicates the following: "Unfortunately, you do not have permissions to access this site. Please contact your system administrator" (see attached) As the administrator I found this odd as he has permission to the document library/group. We then chose "More Option.." above the error message. This then opened the location of the document library where he then saved the file, no problem. So he had the appropriate permissions...why would it indicate he didn't and require him to select "More Option.". Has anyone else experienced this behavior? Do we know why?
