What I got back was very similar to the user mentioned above. After giving the cloud some time to process this change, I signed in and ran a search or two. First I had a test user added to the Microsoft 365 Group currently in use. It does not mean that it will be very usable by other sites.Īfter more searching and finding very little, I decided it was time to do some of my own testing. What it doesn’t tell you is that it’s mostly referring to access to the team site that is created, specifically for that group, when the group is first created. So SharePoint was mentioned in that list of Microsoft 365 apps, right? How could the group type be the problem then? We needed access to SharePoint and it says it does that. Microsoft 365 Groups is a service that enables teams to come together and get work done by establishing a single team identity (managed in Azure Active Directory) and a single set of permissions across Microsoft 365 apps including Outlook, SharePoint, OneNote, Skype for Business, Planner, Power BI, and Dynamics CRM. I decided to do a little research anyway into what that meant. At the time, I didn’t know anything about Microsoft 365 Groups but didn’t really think this could be the problem. It turns out these two new groups were setup as Microsoft 365 Groups instead of security groups. Luckily this random check ultimately ended up pointing me to the real problem. Microsoft 365 Groups vs Azure AD Security Groups
This was a bust of course, but being fairly new to administrating SharePoint Online, I was game for checking all sorts of things I didn’t know about. For some reason, I finally decided to go look at the AD groups themselves with the thought that since roles are assigned to users, maybe the same thing might need to be done for groups. Thus began my long search on all sorts of things SharePoint search related, trying to figure out what was going on. Yet he could easily navigate to and access all the document libraries in all the sites.
#MS AZURE VS OFFICE 365 FULL#
One of their users (and others, we later found out), who had full read access to the root site and all subsites, would only get back results from his OneDrive library and from the separate training documents site (which is open to Everyone). The ProblemĪt first all seemed to work ok but as the week progressed, random problems started cropping up that we couldn’t explain, the biggest one revolving around search results. We then granted SharePoint permissions to the new AD groups by adding them into the appropriate SharePoint groups and removing the reference to ‘Everyone but external users’. Our recommendation to them was to use Azure AD groups so that the groups would be global and could be both centrally managed and used across site collections.Īs we moved ahead with it, they had the groups added with the appropriate members. i also found some other articles that have somewhat conflicting information.We recently had a client who was ready to streamline the security of their SharePoint Online site and change it from ‘Everyone’ access to groups of people with more specific access. i'm hoping for clarification for that vs the other azure ad versions.īelow are a couple excerpts from articles i found on the topic.
#MS AZURE VS OFFICE 365 LICENSE#
Should now be available to all o365 users regardless of their license or azure ad version (except free) being used.Īlso, i recently saw mention of azure ad " office 365 apps only" in one article however cannot find a definition of what that flavor of azure ad actually is. they currently have e1, e2 & e3 licensed users.
#MS AZURE VS OFFICE 365 PASSWORD#
I'm working with a company who has an o365 cloud-only tenant (no azure ad connect or sso) and they want to enable self service password reset for their o365 users.
0 kommentar(er)
