Monday, April 30, 2012

Office 365 DNS

There are quite a few DNS changes to be made to prepare for Office 365. One way to test to see if the DNS is setup properly is through this new site:

Just enter the URL of your office 365 site and it provides a report. Great site and very helpful.

Tuesday, April 24, 2012

Office 365 Change Account Suffix

Taking a break today from the mobility subject - will return to that on the next posts. I just wanted to pass along a fairly common issue and how to resolve it in regards to Office 365 Account/Domain Suffix.

A user signs up for Office 365 and has all of their DNS information (for the purpose of this blog, we will say: When registering for Office 365, an administrative account is created with the suffix of

This blog will not document the DNS changes to be made, but let’s just say those changes are completed.  Now, we want to use our domain ( as opposed to for login purposes (and email purposes as well).

In the upper left hand corner of the Admin Page, select your domain name (john here):


On the next screen, select Edit:


Select the drop down list next to Primary Verified Domain and select the non selection:

Select Ok (in the lower right hand corner):

 Now all of the user accounts created from this point forward will have the new suffix.

Happy Computing!

Monday, April 23, 2012

SharePoint/Office 365 Mobile Access ' Cont

When last discussing mobile connectivity, I mentioned ensuring a business case for this functionality. Now let’s assume that a business case has been presented and warrants remote access, what then?

There are some questions that need to be asked even before proceeding to the utilization of Office 365 on a phone or tablet.

1.       What type of access is needed? Do users need to be able to only view data or is editing the data a necessity as well?

2.       Will data be added to the site remotely?

3.       If data is to be added, what type of data, documents, InfoPath form data, etc?

4.       What type(s) of devices will be accessing the site?

In doing our research first, it will help us to leverage the proper solution for the business need. One of the biggest challenges that I see is the lack of information gathering in the initial stages of solution development.  By asking these key questions, we can save ourselves some headaches later on.

The next blogs will focus on the user experience based on different mobile technologies: iPad, iPhone, Android and Windows Phone.

Friday, April 20, 2012

SharePoint Team Site Mobility

Accessing data offsite via phone, tablet or laptop is now the norm. In Office 365, the SharePoint Team Site can be accessed utilizing any of these technologies. However, functionality varies based on the device. My Android phone has a much more limited experience than my iPad.

Mobility in and of itself is neither a business case nor a strategy. The first question to ask is what is the business need? Has an employee or group of employees requested remote access to data stored on the SharePoint team site? If so, why do they need remote access for that? In most cases there are justifiable reasons to warrant researching mobile access further but a coolness factor is not one of those reasons.

In future blog posts, I will examine the user experience via an Android Phone, Android Tablet, and an iPad. Before we go down the path of mapping out a mobile strategy, we need to identify the problem we are trying to solve. That is the purpose of technology anyway – solving business issues and making the business run better.

Monday, April 09, 2012

Office 365 and Android

There have been several reports of users having issues setting up their Android phone to access their Office 365 email. I am one of the users that experienced an issue with setup and I wanted to pass along the solution that worked for me.

On my Android, I went to Add an Account and the Exchange server setting, To discover the proper server value, I accessed my Office 365 email via the web browser ( In the URL, the Exchange server name is listed:

Use this as the Exchange server name on your Android device and the Microsoft Exchange Activesync should connect. There have been several other posts about other Exchange server addresses that worked for others but this is the only solution that worked on my Android device. 

Sunday, April 01, 2012

Connecting to Shared One Note Notebook

In my last post, I covered how to share a One Note notebook via SharePoint in Office 365. Our consulting group was tasked with upgrading a major client system. We needed to thoroughly document our client meetings and One Note was our tool of choice. After the meetings any other meeting attendees could add needed information (provided they had access).

Now back to our subject, how do users connect to a shared One Note notebook?
2    Navigate to the Office 365 Team Site Document Library where the One Note notebook is located.

Hover to the right of the document name until the down arrow appears and select Edit in Microsoft One Note:

3 An Office 365 login screen will appear, enter your username and password:

4.       The notebook now opens in One Note
5.       If several users have made changes to the One Note notebook, it will be denoted on the right hand side of the page. In this case the blue line represents entries by my account the LA represents entries by my co-worker:

6.       If One Note is not installed locally, then select the View in Browser (or Edit in Browser) option to use the Office Web Client. Please Note the ability to view or edit in Office Web Apps is dependent on the version of Office 365 that is being utilized. That is a blog subject for another day.

That’s it; you are now connected to the Shared One Note notebook collaborating on notes. Stay tuned for a brief overview of versioning using this solution.