My name is Emily Parrish. I specialise in cloud security and have recently been expanding into the field of digital forensics and incident response (DFIR). I’ve been working in IT for around 15 years in some form or other. I am a hunter, a trainer, and I am passionate about my field 😍

I started this blog in order to give back to the IT community who have helped me so much during my career, and to provide myself with a cheat sheet for common problems.

16 thoughts on “About

  1. Noam Hassan says:

    Hi Emily, very interesting blog/s. I don’t know if you or anyone has come across the issue I’m having? I’ve just installed MS EX 2013 and it’s working fine, but when I went to connect Outlook to it, I receive an error. Basically it just won’t connect to OL, OWA is fine.


      • Noam Hassan says:

        Wow! Thanks for the quick response, I’ll have a look at your link. One thing I’ll mention though is I’d setup a trial for 365 and had to setup autodiscover to point to autodiscover.outlook.com. and now I have Ms EX 2013 on-premise am not really sure where this should be pointing to? I did try putting our WAN address in but it didn’t like it.


      • Ex2013 won’t work if you’ve got your autodiscover records pointed to Office 365. What you should do is:
        – Internal DNS – point to the internal IP address of your Exch 2013
        – External DNS – point to the public IP of your Exch 2013
        You can also use testconnectivity.Microsoft.com to test Autodiscover.


  2. Noam Hassan says:

    Cheers Emily, well I’m now trying to point autodiscover for our domain to our public IP and would you mind detailing exactly which records I need to create/amend? I’ve just created an A record for the autodiscover (public) and have a CNAME of autodiscover pointing to autodiscover.


  3. Dave C says:

    Hi Emily,
    I hope your well. you helped setup our systems to work with Office 365 a couple of years ago now. We are using Azure AD sync as you set up for us but our main issue is when users change their passwords, when they next log back on they then have to enter their new passwords sometimes around 5 or 6 times for Outlook, Skype, OneDrive, etc. as you can imagine is not great experience for the user. Is there a better sync tool out there to handle single sign-on type connections like this between our co-lo Active Directory and Office 365?


    • Hi there Dave, you’ll have to give me some clues so I know which customer this was for as I can’t work it out!

      A user password change should get communicated to Office 365 within 2-3 minutes and once this has been done there should be no further delay. If you are having a longer delay than this then it is likely that something is wrong!


      • Dave C says:

        Sorry Emily I work for Dewhirst. It is not the delay that is the problem I don’t think, the new password is accepted but why does it pop up in around 5 or 6 places once the user has signed onto their computer using Active Directory?


      • Ah of course! Hope all is well up North 🙂 So the reason this is happening is because you are using Password Sync, and not ADFS. If you wanted a proper Single Sign On experience then ADFS would be the option for you. This will get rid of all those annoying password prompts for using inside the network 🙂


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s