How to work with O365 groups in SharePoint Online

Today I’ll post about SPO working with O365 groups, for some people will be a bit confusing, but we’ll try to disperse this doubts. So let’s begin:

Firstly I created a group into OutlookO365 groups tab, and edit the members

spo1spo2

After the groups have been created, let’s begin to dismystife something 🙂

We can use SPO groups to give permissions in a site, site collection, or also to give permission or share a document

spo3 spo4 spo5

But… I have detected some things that would be nice if in a future would be implemented, for example, is not posible to mention a O365 group in the newsfeed 😦

spo6

Bonus: Every time you share a document with a group, all the members of the group will be notified that has been shared a document with them

spo7

spo8

Despite the newssfeed in SPO, in the Groups notification is it possible to follow a conversation

How to use external users in SharePoint Online

Hi all!! Today I come with a Little lab that would be very useful for us, in this case we are planning to share some site from O365 to external users (no problem), but this users would have an Azure account in our AD, so it’s easy to control what are they doing or simply to change their password or any other action.

The article in question is the following: http://blog.atwork.at/post/2014/12/06/How-to-use-external-users-in-SharePoint-Online-with-a-cost-free-Azure-Active-Directory.aspx

Also, you’ll lear how to add an azure subscription to O365, I already tried, and works like a charm 🙂 So I encouraged you to try it.

Cheers!

Set up the Trust with Office 365

We must now open PowerShell to convert the domain we previously added to Office 365 to a Federated domain.  You’ll want to run Microsoft Online PowerShell as Administrator.

Type $cred=Get-Credential and hit Enter.  This cmdlet prompts you for credentials. Type your Office 365 administration account credentials.

Connect-MsolService –Credential $cred

The following command will convert your domain into a federated domain

Convert-MsolDomainToFederated –DomainName demos.local

If successful, you should see the message: Successfully updated ‘demos.local’ domain

If for any reason you need to go back to your previous standard domain, you have to type the following command:

Set-MSOLContextCredential -MSOLAdminCredentials $cred Convert-MsolDomainToStandard –DomainName demos.local –passwordfile password.txtSkipUserConversion $true

In case you need to update the ADFS connection, you have to type the following command:

Update-MsolFederatedDomain -DomainName demos.local

To configure an administrator user to not to expire the password, type the following command:

Set-MsolUser -UserPrincipalName  office365@yourtenantdns.onmicrosoft.com -PasswordNeverExpires $true

After doing that, the next step is to Enable the Directory Synchronization. This will be explained in a future post 🙂

Implementing AD integration with Office 365 using a sub-domain (for dev/test)

The other day I found an interesting article from Chris O’Brien to create multiple tenants of O365 for dev or test, in a subdomain

Before start, be sure you have or you know the person that has the permission to do the following:

  • An Office 365 tenant ready and provisioned (could be a 30 day trial)
  • The top-level domain (e.g. MyCompany.com) – this needs to be something you/your organization already owns and has registered
  • Ability to manage DNS for the domain (usually at the ISP hosting the domain)
  • Ability to create user accounts in the AD you’ll use

Hope it helps