Running a Secure Service

The Ask Perry blog is alive!  In this edition I spend time discussing a topic I frequently hear from customers, "how do we run a secure Office 365 service".  I am joined by my new host Julia White to review this topic both from a data center view and from a customer control perspective.

Here are few of the questions we discuss in this edition.  Hit up the video to get the full conversation.

Is Encryption the silver bullet to provide a secure and private service?

What are the physical containers and logical boundaries to reduce risk in the service?

How does the service employ the concept of "functional boundaries"?

How does the concept of “searchable encryption” work with the service?

Does the concept of a customer controlled encryption key really reduce risk in a service?

What features does the service provide enabling to reduce a customer risk?

You can expect to see the frequency of posts return to normal on the blog.  Additionally I want to remind you that MEC 2014 is less than 7 weeks away.  I will be part of the MEC experience and I invite you to join me in Austin, TX.  Go to to register today. 


Comments (4)

  1. Anonymous says:

    Perry Clarke is back to geek out with you through his blog and the Geek out with Perry video series.

  2. Kris Smith says:

    What happens when the government shows up with a Foreign Intelligence Surveillance Act (FISA) request? it was indicated that the only way data cannot be provided was through a customer work flow action.

  3. Steen says:

    Message Encryption – do you have more info on how? If the recipient is in Exchange Online I can see how. But if the recipient company have an on premise Exchange – how to you do the encryption on Exchange level?

  4. bill says:

    Who has the Encryption Keys here?
    If the Vendor (Microsoft) has the Encryption Keys, this feature is Worthless & just Marketing.
    Also per NSA PRISM revelations, Microsoft shared encryption keys with NSA.

Skip to main content