About
This blog is my personal space to talk about Microsoft Technologies, specifically Office 365. I will also be blogging about other things that interest me.
More About Me:
I am a Managing Consultant with Catapult Systems. I have over 15 years of professional experience with the last 11 in Microsoft Infrastructure technologies. My primary areas of expertise are Windows Server, Microsoft Active Directory, DNS, Exchange 2007/2010, PowerShell and virtualization with Hyper-V. I am also the Office 365 Technical Evangelist for Catapult Systems; in this role I am responsible for all things Office 365. I have done numerous Microsoft Infrastructure assessments, Active Directory domain consolidations and migrations and Exchange 200x to Exchange 2010 migrations. I have worked with Microsoft Online services over the past three years plus with BPOS and now Office 365. Clients that I have worked with range from small 50 seat organizations to large companies with over 10,000 seats worldwide. I currently holds three MCITP certifications (one being for Office 365) and six MCTS certifications.
I am one of the founding members of the Office 365 International Users Group, http://www.office365union.com.
I was also awarded as a Microsoft MVP for Office 365 July 1, 2012.
The Family
Hi Sean,
Great blog you have there!
I wrote a very cool application for the Technet community that automate account provisioning process and It supports Office 365 also. I called it poor man’s Identity management solution. It would be great if you can write an article or review for this application on you blog.
http://gallery.technet.microsoft.com/Z-Hire-Employee-Provisionin-e4854d6b
Let me know.
Thanks
Hello,
I came across your blog while trying to resolve an issue with 365. During my trial, I noticed that I could not save an email attachment into sharepoint. Nor can I attach a file from sharepoint into outlook exchange on 365. Ironically, with windows 8 and sky drive, I believe you can.
I was very excited about switching to office 365, windows phone, and Microsoft dynamics crm. This would provide a totally web based solution. But, the lack of integration between outlook and sharepoint in 365 is a deal breaker. I will stick with android phone, google docs, and sales force.com.
Am I missing something here. I seems that Microsoft is unwilling to untether us from Office being resident on a pc. Too bad.
I welcome your insights. Thanks.
Rick
Rick,
I think I understand what you want to do, receive an email with an attachment and save the attachment directly to SharePoint without saving local (to your local hard drive) and then upload to SharePoint, is this correct? With the current version, Wave 14 of Office 365, this is not possible. But What I will say is that you have several options with the next version of Office 365, Wave 15, due to be available the first quarter of next year. You could save the file to SkyDrive Pro local which would be sync’d with one or more Document Libraries in SharePoint. Another option would be to setup a Site Mailbox in Exchange and SharePoint, then forward the message to the site mailbox and the attachment will be saved in SharePoint.
Hope this helps
Sean
Hey scott,
read a couple of your posts and they are very insightful and helpful. have a quick question related to adfs proxies.
I’m trying to chain an ADFS Proxy in my external DMZ to an ADFS Proxy in my internal DMZ so that communication can ultimately flow to my ADFS server located in my internal DMZ. I’m see traffic get to my internal proxy, but nothing is relayed over to my internal ADFS server. Have you ever worked on such a configuration before?
Thanks in advance for any thoughts, suggestions, and your time.
Tony
Tony,
I have never tried this and do not believe it will work. The ADFS Proxy can only talk with a full ADFS server, not another ADFS Proxy. I would recommend allowing the External DMZ ADFS Proxy to connect directly with the intern ADFS Server.
Thx. Was just trying for greater segregation away from the internal AD store. Would this architecture support the following use cases: 1. Remote VPN employees that terminate to the external Fw? 2. External organizations that are interfacing with an SSO enabled app? 3. Internal users from within the internal network domain.
Tony,
Should work. One note, the internal Users should be going directly to the Internal ADFS server(s). This is handled by having the URL for ADFS in the internal DNS point to the internal ADFS Server(s).
Warning: Problems with Microsoft’s Office 365 service upgrades for existing clients. I posted this on their Office 365 Service Upgrade forums: http://community.office365.com/en-us/forums/156/t/148092.aspx
3+ weeks of serious problems since the “upgrade”.