Office 365

PowerShell for Office 365

Hiya; Have you moved into Office 365? Oh you did!

Then you are already aware of all the fun things you can do and some of the ones you can’t without the use of powershell commands

Thankfully Microsoft and the Office 365 team have released a new site titled PowerShell for Office 365 which targets Office 365 IT administrator who is new to PowerShell.

They get you started by having you download the right tools to your local computer. Here is a list for starters.

  • Download Microsoft Online Services Sign-in Assistant to sign into Office 365.
  • Download Azure Active Directory (AD) Module so that you can perform administrative tasks in Office 365.
  • Download SharePoint Online Module so that you can manage SharePoint Online.
  • Download Skype for Business Online Module so that you can manage Skype for Business Online.

So go have a look and happy learning and Administration of Office 365

For more info: http://powershell.office.com/

 

Office 365: EX21073 – Investigating

Incident and Reported Details

Incident ID: EX21073

Details:

Current Status: Engineers have completed developing a fix for the issue and are now testing it prior to deployment across the affected environment.

User Experience: This issue does not affect end users.

Customer Impact: Customer impact appears to be limited at this time. Affected tenant administrators are unable to view the Compliance Center page when navigating from the main Office 365 portal when using Chrome or Firefox internet browsers. As a workaround, upon encountering this issue, users may attempt to access the affected portals directly by cutting and pasting the resulting URL into a new tab or window. The affected URL is: https://compliance.protection.outlook.com/

Incident Start Time: Sunday, April 12, 2015, at 3:00 PM UTC

 

Office 365: EX20870 – Restoring service

Incident and Reported Details

Incident ID: EX20870

Details:

Current Status: Engineers have found that a portion of the affected infrastructure did not upgrade to the latest version as was intended. The remaining server capacity is now being updated. Once this is complete, engineers will run additional tests to confirm the update resolves the underlying root cause.

User Experience: Affected users are intermittently unable to connect to voicemail. When attempting to connect, users will hear silence and the call will disconnect.

Customer Impact: A few customers are reporting that they are experiencing this issue. This event is affecting customers with on-premises Edge server deployments utilizing the Exchange Online Unified Messaging (UM) feature.

Incident Start Time: Wednesday, April 1, 2015, at 8:00 PM UTC

Preliminary Root Cause: As we continue to expand Office 365 services and onboard new customers, an issue with the way the infrastructure handles connections has been revealed. Under increased load, the service performed at a suboptimal level handing connection requests, which caused increased latency and disconnects.

Tech Short: Use Dsquery tool to manage group memberships On-Prem to Office 365

 

I had mentioned in a previous post about the inability to self service groups.

Problem: on-premises distribution group is synced to a Microsoft Office 365 organization through Active Directory synchronization, migrated users who are owners of the distribution group can’t manage it in Microsoft Exchange Online

Solution: Use the Exchange Tools (But we no longer have exchange on prem?)

Solution: Use Active Directory Users and Computers

Solution: Dsquery.exe  – Press the Windows Key and R to open the run box and past in the following:

Owners of the group should be able to make changes when needed.

Note:  You will still need to wait for dirsync to complete.

kb2417592

Office 365: Self Service of Distribution Groups

The ability to self service the creation of distributions groups has been a feature for quite some time in my Exchange experiences.  Now that I am in Office 365 / Exchange Online this functionally is no longer available for synced groups. This now forces the enlistment of the support department to facilitate all mortification for the end user.

Looking into this to get an understanding as to why this is, I’ve learned that if you’re an Office 365 Exchange Online customer and currently utilizing Directory Synchronization (DirSync) between an on-premise Active Directory and Office 365’s Azure Active Directory you will face such incidents as the objects on the Office 365 are in read only mode and are updated via the synchronization that has been put in place

You are even given a a little message when you attempt to make modification to groups:  The action ‘Update-DistributionGroupMember’, ‘Identity,Members’, can’t be performed on the object ‘Group Name’ because the object is being synchronized from your on-premises organization. This action should be performed on the object in your on-premises organization.

Now aware of this limitation that exist around group modification due to them being read only how do I work like this? I have the following two ideas to work with.

One: 

One method is to go old school and use the Use the ‘Find Users, Contacts and Groups’ tool to allow group modification. However there is an issue regarding the fact that the computer used needs to be a member of the domain and at the time of change also connected to the on premise domain network (internal or via vpn).

Note: After changes have been made the condition of waiting for Directory Synchronization (DirSync) to complete its sync cycle must take place.  This can take up to 3 hours time.

 

Two:

The Second method is to change all Directory Synchronization (DirSync) Distribution Group Objects to the Azure Active Directory and make the On-Clound