Multi-factor authentication (MFA) is a security system that requires more than one method of authentication from independent categories of credentials to verify the user’s identity for a login or other transaction.
In Office 365 the way MFA works is that you use your normal username & password but after you have verified that factor of authentication you are then sent a text message (SMS Message) to your mobile phone with a code to enter into the login screen.
This increases security because if someone does find out your username & password they still cannot login to your account without your mobile phone.
Setting up MFA on Office 365
You will need to be an administrator of your office 365 tenant to set this up.
MFA is a free service that you get with Office 365. At the very least you should have MFA enabled on all administrative users and if you can you should have it enabled on all Office 365 user accounts.
Azure Files is Microsoft’s answer to the typical on premise file server file share.
Using the SMB 3 protocol to connect your computers, laptops and servers to a file “serverless” file share in the cloud.
I have been using Azure Files to connect sites together for large data migrations, where I used to use a VPN, I now just use an file share straight from Azure which has been really easy to manage, just map the network drive and once your done un-map the drive.
I haven’t actually used this in production yet, and I am not sure how it will perform with a lot of users connected but it is an interesting concept. I’m also not sure about how to keep this secure, I need to look into that further because if you have say 30 computers with a mapped network drive and they are all using the same credentials what happens if one of them gets compromised?
Does that then mean that someone has the key to access all of your files? Something that I still need to look into… Either way once I do I will update this post. If anyone reads this and does know I would be interested so leave a comment or touch base with me on LinkedIn or email.
This video shows you how to make a new Storage account, create a file share and connect it to a computer using a mapped network drive. I also show you how to download and install the Azure Storage Explorer and use it to browse your newly created file share.
A Note on Azure Storage Explorer: I did some testing and it turns out you cannot look at your on premise network locations in the program, just (as the name suggests) Azure Storage.
This issue occurs because there has been a lock placed on the Azure resource you are trying to delete.
Azure sometimes places locks on linked resources or you or another administrator of the system may have put a lock on the resource.
What is a resource lock?
Basically the resource locks stop you from acidentily deleting an Azure resource, it i good practice to put resource locks on production Azure resources to protect from accidential deletion & you can also put notes on the lock so who ever is trying to delete it can see why the lock was put on initially.
How to remove Azure Resource lock so you can delete the Azure resource?
Open the resource you want to delete and select Locks – This is in the settings part of the blade.
Read the comment on the Resource Lock to see why it is applied, if it is safe to delete then you can click the three dots on the right of the Lock and click delete.
Now the resource lock is removed from the Azure Resource, you will be able to delete it.