CIAOPS Need to Know Microsoft 365 Webinar – January


Join me for the free monthly CIAOPS Need to Know webinar. Along with all the Microsoft Cloud news we’ll be taking a look at Defender for Business.

Shortly after registering you should receive an automated email from Microsoft Teams confirming your registration, including all the event details as well as a calendar invite.

You can register for the regular monthly webinar here:

January Webinar Registrations

(If you are having issues with the above link copy and paste –

The details are:

CIAOPS Need to Know Webinar – January 2023
Friday 27th of January 2023
11.00am – 12.00am Sydney Time

All sessions are recorded and posted to the CIAOPS Academy.

The CIAOPS Need to Know Webinars are free to attend but if you want to receive the recording of the session you need to sign up as a CIAOPS patron which you can do here:

or purchase them individually at:

Also feel free at any stage to email me directly via with your webinar topic suggestions.

I’d also appreciate you sharing information about this webinar with anyone you feel may benefit from the session and I look forward to seeing you there.

My software and services 2023


Here’s last year’s post for comparison:

My software and services – 2022

My PC’s are either running the latest version of Windows 10 (22H2) or Windows 11 (22H2) without any issues. Some machines cannot be upgraded to Windows 11 and some I have left at Windows 10 for the time being to verify their operation. I no longer run any Windows 10 Insider builds as I had trouble backing out of these when I needed to. I still have Office Insider builds happening in my environment.

All Windows machines are directly joined to Azure AD and managed via Intune and Microsoft Endpoint Manager, except for one that remains stand alone for use with my IoT projects.  The Azure AD connected configurations are based on the Windows MDM security baseline settings. All machines only use  Windows Defender for local security monitoring and management. Thanks to Microsoft E5 on my production tenant, I am also using Microsoft Defender For Endpoint at the back end for monitoring and investigation of endpoint threats.

My two main tenants are an Office 365 E5 demo and Microsoft 365 production environments. A mix of Windows 10 Pro and Enterprise machines are all Azure AD joined to the Microsoft 365 production domain. The production Microsoft 365 tenant has Microsoft 365 Business for all users except myself. I have a Microsoft 365 E5 license on which I have configured all the services including integrated PSTN calling via Switch Connect.

I use Microsoft Sentinel to monitor threats across my environments via a single pane of glass. I have also now added Defender EASM.

I use the following major browsers:

Edge – my primary browser across all my devices including iOS and Android. I have it locked down with baseline policies via Microsoft Endpoint Manager.

Brave – I have become increasingly concerned about the surreptitious tracking that many sites perform, especially when it comes to social media sites. I therefore now do all my ‘random browsing’, searching and viewing of social media sites.

– Firefox – I now only use this on my Surface Pro X because Brave doesn’t offer an ARM version.

I have now cranked Edge up to the maximum security level but wanted to isolate the most likely tracking culprits into another browser that was security focused. After some evaluation, I have chosen Brave to be this browser. This is now where I do all the stuff that is more likely to be tracked and now hopefully blocked or at least minimised. I have also set this browser up to use Duck Duck Go as the default search engine, otherwise I use Bing for my production Edge browser. I have completely eliminated Google Chrome off all my machines without any issues and recommend those who are becoming more concerned about their privacy, like me, do the same.

Services like SharePoint Online and OneDrive I use regularly both in the demo and production tenant. I have the OneDrive sync client installed, running and connected to various locations on my production and demo tenants. I can now sync across all my different tenants as well as my consumer OneDrive storage. I have common places pinned to my Windows Explorer Quick access, which I find to be a real time saver.

I regularly use Microsoft Teams which is now my main messaging application. All the CIAOPS Patron resources like the intranet, team, etc all reside in the Office 365 E5 demo tenant but I connect to it on my desktop normally via an Azure B2B guest account from my production tenant. Thus, I can admin the Patron resources in a browser if need be but I get the same experience on my desktop as any Patron would. Handy to know what works and doesn’t work with Microsoft Teams guest access. Thanks to Microsoft E5 and Switch Connect, I also have Teams connected as a phone.

I use Lastpass to keep my passwords and private information secure. It allows me to do things like generate and store unique passwords for each website that I sign up for. It is also available across all browsers on my machine (including Microsoft Edge). I also now also use Lastpass to store secure notes. I will admit that recent security breaches with Lastpass have me concerned and I start exploring an alternative password manager.

The extensions I run in all my browsers are:



Duck Duck Go Privacy Essentials

I use Microsoft Power Automate for automation as well as Azure Functions.

For my email newsletters I use Mailchimp.

My preferred public social networks for business, in order are:

1. Twitter

2. Linkedin

3. Mastodon

I consume a lot of content from YouTube both for business and personal interest. I also also use YouTube extensively for my publicly available training video training.

Microsoft Office desktop software is still part of my everyday workday via applications such as Outlook, Word, Excel, PowerPoint, etc. I use the desktop version of Outlook on my Surface Pro 7 which lives on my desk but I only use Outlook Web App on my travelling Surface Pro 6 device. I could happily not use Outlook on the desktop any more I believe but I still use so I understand the experience for most users. However, I do see the day when Outlook on the desktop begins to lose its appeal.

One of the things I have added to my desktop version of Outlook is a digital certificate that signs every email that I now send. This helps the receiver confirm that the message they have received is in fact from me and that it hasn’t been altered in any way. There are some issues when people attempt to reply to these emails from a mobile device but I believe a fix from Microsoft is coming..

The key application from the suite for me is OneNote. OneNote is my go to Swiss Army knife for just about everything digital. I use it to capture all sort of data. I even use it as a diary as I have detailed previous here:

One of the ways I use OneNote

The reason OneNote is key is because:

1. Just about everything I put in there us searchable

2. It is freely available across all platforms.

3. All my information is synced and accessible on all devices.

4. It is available on the web or offline if needed.

I am a big user of OneNote on my mobile devices. This combination has allowed me to totally eliminate my paper notebooks for things such as journaling.

I use Pure Text to easily paste information, especially to and from OneNote as only text.

I am now a big Microsoft To-Do user. I use it to keep many tasks and items that I need to follow up. I love how it is available on all my devices and syncs across them all as well.

I use Windows terminal now for things like PowerShell execution and Microsoft Whiteboard for demonstrations and training.

Microsoft PowerToys allows me to customise my desktop layouts using FancyZones, for those machines that are not running Windows 11 where this functionality is effectively included.

Another key service I use everyday along with Microsoft 365 and OneNote is Azure. Typically, I use it for running up virtual machines that I test various things with but I also use it with my IoT projects.

I use Microsoft Sentinel to monitor all my services and machines in one single console and tell me about any incidents now along with Defender EASM to search out vulnerabilities.

There is just so much that can be done with Azure and I pretty much use it everyday.

All of my data now lives in Microsoft 365 protected with things like Windows Information Protection and other Microsoft information protection options. All my Windows machines run with full disk encryption thanks to Bitlocker.

I have implemented Windows Defender Application Control (WDAC) to provide application control to improve security in my environment.

To capture my desktop for my online training academy or my YouTube channel I use Camtasia. I use SnagIt to capture screen shots and add highlights and emphasis to these. Snagit allows me to capture complete screens or specific areas quickly and easily.

I use Microsoft Teams to record my podcasts, which I then produce with Camtasia. These are uploaded to Podbean where they syndicated across various network.

To compose and publish blog articles I use Open Live Writer. My blog lives on

My web site and Battlefields site live on Squarespace.

The majority of images I get, like the one at the top of this article, I get from Pexels. Pickit is also another great option.

For improved meeting management productivity I use Microsoft FindTime.

My Surface Duo 2 device is connected to my Surface Pro 7 using the Microsoft Your Phone app making it super easy to interact with the phone while on the desktop. I really wish they have this capability for the iPhone, but I’m not holding my breath,

I use Visual Studio Code in which I do most of my PowerShell editing and publishing. I also use it now for my IoT projects. The end result typically is my GitHub repository where you will find a range of scripts and other resources that I maintain regularly. With Visual Studio Code I can edit publish and sync all my machines and my GitHub repository no matter where I am. Very handy.

Here are also a few of the other items I use regularly that are not for business:

Amazon Prime Video – only place to the latest The Grand Tour action. I also liked the Jack Ryan series and well as the Gymkana Files but most of this viewing is now on my iPad mini.

NetFlix – Seen a lot of great stuff this give all the time in lock down but most of this viewing is now on my iPad mini.

XBox Live Gold – access to all the online Xbox goodness.

Duolingo – language learning, Japanese and Italian at the moment but most of this access is now on my iPad mini.

Duolingo Math – for keeping the brain sharp.

Kindle app – for typically reading books on my iPad

I try and keep my production machines as ‘clean’ and free of unused software as possible. I ensure that they are updated regularly. Any software testing that I need to do is typically done on a virtual machine in Azure.

So there you have it, the major software and services that I use regularly. I continue to search out additional software that will improve my productivity. If you use something that you’ve found really handy, please let me know and I always keen to explore what works for others.

My Gear 2023

You can take a look back at last year’s gear here:

My Gear 2022

there were/are some major changes happening with my assortment.

Surface Duo 2 – My ‘Google’ phone. This as a ‘secondary’ or backup phone. It has all the Microsoft apps installed on it and is connected to my Microsoft 365 production account. Most importantly, it has the Microsoft Authenticator app for MFA access for certain apps.  I also have the latest Microsoft Surface pen which I really like. It is probably the best ‘electronic scribing’ device I have used.

i have to admit that I haven’t used this device that much since I bought it. Some of the reasons for that were that I planned to use it as a writing device (i.e. notepad) but storing the pen with the device has proved problematic. yes, it does have a magnetic area to hold the pen but you can’t just throw the device in a bag and expect the pen to be still connected. The pen really needs some form of pouch in which the pen lives so it can always be with the device. The other thing is the large camera bump prevents the device from laying completely flat. This makes it very hard to use as a replacement notebook on a desk. One of my resolutions this year will be to try and use this device much more to get full benefits from the investment made as I do really like the device and feel it can serve a real purpose for me. I just have to work out how to reduce the friction of using it everyday..

iPhone 12 Pro Max – Is my main mobile device. Unfortunately, there is a growing crack on the screen that I believe was initiated by the Surface Duo 2 camera bump, when the devices where in my laptop bag together. The phone still works and the crack is off to one side of the screen but I can see the crack growing and full expect one day to have to replace the device. I want to delay this as long as possible since I have invested in a Quad Lock case and multiple holders (car, desktop, etc) for this case. A new phone will mean a new case, which isn’t the end of the world, just additional hassle.

One thing that I have configured my iPhone for is default grey scale display. I do this for two major reasons, firstly to prevent the phone from grabbing and holding my attention and secondly to save power. With the colours disabled on your phone it is amazing at how les tempting it is to play with it and use it as a crux when you are bored.

The great thing I will say about about iDevices is their battery life. My experience is that this allows them to work for years and years, providing great value.

Surface Pro 7 – This is my main desktop machine. Being the same form factor, it just slotted directly into my Kensington SD7000 Surface Pro Docking Station I already have in place. This machine runs Windows 11.

I am considering a potential Surface Pro 9 purchase, however as of yet I can’t really justify it. The other downside of going to a Surface Pro 9 is that it won’t fit in my Kensington SD7000 Surface Pro Docking Station which I really love.

Surface Pro 6 – My backup and travelling machine. I use it pretty much every day as an adjunct to my main machine. It lives on my secondary Kensington SD3500v docking station connected to a full screen and acts as my backup in case my main machine fails or is unavailable for some reason. It is also a handy way to test things from outside my environment by hot spotting to my phones. This machine run Windows 10 but could run Windows 11. I haven’t upgraded as yet because I want to maintain at least one production machine on Windows 10.

This is the machine I am considering replacing with a Surface Pro 9, given that it will plug directly into the existing Kensington SD3500v docking station. The question then is, what do I do with the Surface Pro 6? It still works. How can I make best use of this device if I no longer use it as my travelling device and backup? That, I haven’t figured out yet.

Surface Pro X – I use this machine as a ‘lite’ travelling desktop as well as a whiteboarding machine for demos and training. Give that it comes with the Surface Pen and has a nice large screen and will lie flat it makes the prefect device for scribing. I also use this device for writing note into places like OneNote. Perhaps not the most effective use of the device but it beats the iPad when it comes to scribing hands down in my books. This machine runs Windows 11.

This is another machine that I haven’t used as much as I want to. I am considering converting it to a full time desk notepad for writing (given it has a Surface Pen which I love). Last year saw the keyboard fail and I agonised over whether to replace it because it ain’t cheap. In the end I did buy a replacement keyboard to main the most functionality with the device. The problem is that if I use it as a dedicated desktop notebook device (i.e. flat on the desk with the cover removed) then it tends to get in way. I think I just need to spend some more time with the ergonomics on my desk to get the most productivity and use from this device going forward.

Surface Pro 3 – Continues to work fine and function as a test machine in my production environment. This machine has now been removed from my production network and operates stand alone. It does this so it can run my IoT project work. I found that with the security I have on my production network that I could not easily operate the IoT software I needed so the simple solution was to remove it from the production network and use it stand alone. This machine is slow and clunky, but for now it is doing the job it needs to. This machine is not suitable for Windows 11.

Surface – I have had an original Surface version 1 for many years now. The keyboard has long since broken by the system still works fine, although somewhat under powered with only 4GB of RAM. This machine is now a dedicated device on a separate test tenant. This allows me to test Autopilot and other settings on it regularly. This machine is not suitable for Windows 11.

iPad mini 5th Gen – I decided I wanted a smaller ‘notebook’ size table to use like a paper diary, amoungst other things, so I went out and bought an iPad mini.

I also now use this iPad mini with the Apple pencil, which generally works well. The secret is to get a good case for both the iPad mini and the pencil. My choice was:

Finite Case with Pencil holder

which I’d certainly recommend as it is flexible, tough and cheap.

The only major downside of the iPad mini is that battery life is a lot less than the full size iPad, which is understandable. I have however never run out of juice but you do notice the power levels fall away quickly when compared to the full size version. I like that the iPad mini comfortable fits on my desk, works will with the Apple pencil and is much more transportable than the larger version. I was a little concerned that the screen size would be too small to enjoy movies and read web pages, etc but that hasn’t proved to be the case. I happy use it lying back on the couch to watch a variety of programs and read web sites.

After a number of years the Apple Pencil doesn’t really hold a charge any more. That is disappointing, although I appreciate it doesn’t have a huge battery. This has again increased the friction with me finding a suitable replacement for a paper notebook because every time I want to write something down, I need to charge the pencil up which takes ages. I may look at getting a new and updated Apple pencil but unsure as to whether I can really justify that in line with the plan to use the Surface Duo more.

D-Link Wireless N300 Model Router DSLG225 – to allow connect to the NBN broadband network.

Ubiquiti – I have a variety of Ubiquiti equipment in place including a  Security Gateway. All these have worked flawlessly and I can’t recommend this gear highly enough.

Docking station – I still love my Kensington SD7000 Surface Pro Docking Station. It is a really neat device, that suits most modern Surface Pro devices. It is slim, compact and now all me to have 3 external monitors off the one Surface devices (as you can never have enough screen now can you eh?). I can plug in all my devices, microphones, phones, etc to it and all the cables are hidden at the back. I also like that you can adjust the screen up and down, a bit like a Surface Studio.

Occasionally, one of my monitors goes dark and a few seconds later comes back, kinda like it is doing a reset or refresh. Maybe I need to update some drivers? Apart from that it continues to perform flawlessly.

The original Kensington SD3500v has now moved to work with the travelling PC when it is running in my office and that is also working well, making it a truly ‘plug and play’ experience when I get back from road trips.

Amazon Kindle – Still have this but it has now largely been superseded by the iPad mini for reading books. I still love my Kindle but if I can have one less device then I’m going to take that option. so for now, the Kindle has been relegated as a backup.

Xbox One S – Still use it to watch YouTube, Netflix and Amazon video but now playing more games thanks to Minecraft Dungeons and Call of Duty game.

I didn’t make any major hardware investments in 2021.

The items that I retired from front line operations last year where:

1. WDSentinel

I will admit that I have my eye on a Surface Pro 9 replacement for the Surface Pro 7 depending on how things pan out this year. I doubt I’ll be upgrading to the new iPhone 13 as I don’t see any major benefits for the costs, that is unless the screen fractures. I want to focus on getting the most from my Surface Duo 2 given its price. I also hear rumours of a Duo 3, so hopefully I’ll be able to trade in Duo 2 in if I decide to.

My Stuff 2023

This post is my annual post aimed at bringing the links to everything I have out there on the Internet together into a single place. Here we go.

About me

Social Media

Free Stuff

Regular technical and business information, tutorials, walk throughs, learnings, upcoming courses and more.

Here you’ll find currently almost 200 videos full of tutorials on SharePoint, Office 365, Azure and technology.

Presentations and whitepapers for free download.

Documentation for older versions of SharePoint on premises, especially the free versions and those that came with SBS.

Cloud lecture series is a set of free tutorials, training session and so on that I have provided over the years:

I have number of free GitHub repositories that include things like PowerShell scripts, pricing calculators, reference documents, helpful links and more. You will find all these at:

With over 293 episodes and now in it’s 13th year my podcast focuses on providing you news and updates from the Microsoft Cloud around Microsoft 365 and Azure.

You can subscribe using iTunes or Stitcher. If you’d like to be a guest or know someone who would, please let me know.

Need to Know webinars are held monthly and announced on my blog. These are conducted using Microsoft Teams.

and subscribe to previous and upcoming webinar recordings and resources here:

My free Teams shared channel you are welcome to join. To do so follow the instruction here: 

here you’ll find a forum on the Microsoft Cloud.

Commercial stuff

This stuff helps pay for free stuff above so I appreciate your support for my paid work.

Access to the CIAOPS community for technical support, product discounts and access to the best Office 365 and Azure information

For end user focused training on Microsoft 365 services and applications:

Lots of courses on Microsoft 365, PowerShell, Azure, SharePoint and the like.

General Interest

This accounts sends a tweet to commemorate a significant dates from the Australian battles in France during World War 1.

I’m a big believer in supporting those who want to build their own business but just need a leg up to get started. Kiva is simply and easy way to provide this and I recommend this to everyone.

In 2022 I read over 45 books. That means I do a lot of reading on a variety of topics and with Goodreads you can follow along with the books I’m reading as well as those that I add to my bookshelf. I’ll have an upcoming post on my recommended reads, so watch out for that post coming soon.

  • Xbox gamer tag = director cia

I don’t play a whole lot these days, but when I do I typically play:

– Minecraft Dungeons

– Call of Duty

– Minecraft

If you ever need to send me stuff you can do so via the following address:

PO Box 5
Beecroft NSW 2119

My Bitcoin address is – bitcoin:bc1qwgcr296c7rtjvlpkv9yy5033qjgwwrvttxhtm7

My Ethereum address is – ethereum:0xD7cc991E1f84B625C3723D2965C9948238F5DFe8

Creating Microsoft Teams general guidelines


You’ll find plenty of advice about creating Microsoft Teams and a collaboration environment out there. None of it should be considered absolute but instead, guidelines when creating your own Teams environment. However, the most important rule should be that Teams should be a planned process, not something randomly generated. Actually taking time to think and plan your Microsoft Teams environment will make your life a whole easier.

The first major suggestion is to plan an environment that is wide, not deep as I have outlined here;

Your collaboration structure should be wide note deep

Unlike traditional file server environments, you have the benefit of powerful search functions and AI surfacing relevant material now in Microsoft 365. Having a flat structure also make it easier to re-arrange if you need to down the track and it also make permissions much easier to handle. If you need some form of hierarchical structure for navigation you can create this using hyper links but underneath the covers, keep the structure of what you build as flat as possible. This means creating lots of Teams and SharePoint sites as needed and then linking them together, using hyperlink, into whatever you need, NOT creating subsites.

Also, as I have outlined in

A framework for file migrations to Microsoft 365

Don’t dump your information into a single location, Team , SharePoint site or Library, etc. There are lots of places for collaboration inside Microsoft 365 and certain types of information works better in different places. Break your information up and put in where it makes sense. You have all these areas available to you, use them.

Along these lines, another guideline I can give is that when information requires pure storage (no conversations or chat around it) then use a SharePoint site. If however, there will need to be conversations around that information then a Team is a much better option. For example, a SharePoint site is a great place for an archive, with finalised forms and documents like manuals and marketing material. A Team works better when creating documents that when finalised, will end up in a SharePoint. Using Teams chat correctly will cut down back and forth emails as well as making all these conversations searchable for all members of the Team.

Further, I’d suggest is to limit the depth of the structure to three (3) levels per:

The rule of three

Making a structure deeper than 3 levels generally results in people hunting up and down a structure looking for the information they are after. At the lowest level you should be able to go into a Document Library and see everything, including one level of folders below. Going deeper means you lose the initial context and when you come out you need to get re-orientated again to continue. This wastes time and creates frustration for users.

Next, when you create a new level, Team, Library, folder, etc always ask yourself the question, “Will be this be by function or location”?”. For example, if you want to create a new Team, ask the question. You then decide with Team will be for Human Resources (i.e. function). Then, when you create a channel below that Team, ask the question again. This may result in channels by State (i.e. by location). When you create a folder inside that channel, ask the same question and maybe create folders like CV, jobs, application, etc (i.e. function again)

Asking this simple question at each level provides a surprising logical structure very quickly. This is in fact where I find most people get hung up when creating a new collaboration environment and having very simple guidance you can follow helps overcome this and get on building what you need.

It is also important to follow some basic guidelines when naming each item in your structure.

– Keep the names you use as short as possible i.e. HR is far better than Human Resources

– Avoid using spaces and special characters i.e. Customer-Service not Customer Service

– Avoid having duplicate items. For example calling your Team “Projects” and then each channel something like Project-1, Project-2, Project-3, etc is redundant and consumes space.

Settling on a naming convention prior to creating your collaboration structure is a very worthwhile investment of your time. For example, settling on how to name a location like a state which could be New South Wales, NSW, N.S.W., Nsw, just to name a few possible iterations. Having a consistent approach to how you name all items in your environment will greatly assist users when they are searching for information and avoids duplicated areas. This is why a small amount of timed invested up front planning your collaboration structure pays huge dividends down the track. Unfortunately, I see too many rushing in and just creating items on the fly and then having issues down the track.

Remember, that you don’t have to build the complete structure on day one. What is the minimum viable solution required? Maybe it is something for a limited group of your users. Build it, learn, test, adjust and then move forward. Typically, you are introducing major changes inside an organisation and best method to see how this is adopted is to take a slow and sure approach while seeking feedback from users. You certainly still have your overall plans but taking one step at a time is going to allow you to quickly adjust if you need to.

Don’t forget that you’ll also have to invest in user training as I have detailed previously here:

Stop making your users feel stupid

This will be especially true if you have moved from a traditional server. Collaboration is very different from storage and failing to help users come to grips with all the features Microsoft 365 provides is going to make adoption of any new system hard. Remember, you can create the greatest collaboration structure in the world, but if people fail to use it, then that investment is wasted. In the end, technology serves humans, so help your humans come to grips with the new system and you’ll be surprised at what they can achieve it with. In my experience, the single biggest point of failure when building a new collaboration system is a failure to train the people who will be using it every day. Fail to do that, and you will struggle to make things better.

As I have outlined in

Process for file migrations to Microsoft 365

Assigning permissions comes AFTER you have created the structure. Remember, by default, Microsoft 365 is an environment designed to make it easier for users to collaborate. This means, by default, users are encourage to share, edit, and so on. For example, Teams is largely designed so that all members have the same permissions inside a Team and can read, write and delete documents by default. The more restrictive permissions you wish to apply to a structure the harder it becomes to bend the technology to accommodate this. Can it be done? Of course, but the more complex and restrictive the permissions, the harder it becomes to accommodate these inside a structure. In short, Microsoft 365 is primarily designed to allow people to work together not blocking them from getting to information. Think of it as allow more than deny.

As I said initially, there are not hard and fast rules when it comes to creating a collaboration structure in Microsoft 365. It is a tool that can be structured in just about any way to suit a business. However, following the above guideline, is going to make your life much easier and will mean you are not fighting the technology to achieve what you want. Because you want to create a structured environment it is always recommended that you design this prior to actually building it. Cleaning up afterwards always takes more time and causes more frustration in my experience. Always start simple and build from there.

Hopefully, these guidelines, based on my experience, will help you get the most from your Microsoft 365 collaboration environment. In the end, build something that work for you.

Need to Know podcast–Episode 293

Happy holidays everyone. Hope you are all enjoying the festive season. A few updates from Microsoft including the availability of Teams Premium plus an editorial on industry burnout. I’m seeing more and more IT Professionals becoming burnt out and feeling lost. At this time of the year take some time to look forward and decide whether it is time for a change. Also, don’t be afraid to reach out and share with others what your feeling. If anyone wants to chat feel free to reach out in total confidence via

You can listen directly to this episode at:

Subscribe via iTunes at:

The podcast is also available on Stitcher at:

Don’t forget to give the show a rating as well as send me any feedback or suggestions you may have for the show.

This episode was recorded using Microsoft Teams and produced with Camtasia 2022.

Brought to you by



Join my shared channel

CIAOPS merch store

Become a CIAOPS Patron


YouTube edition of this podcast

Microsoft 365 incident response training

GPT Chat

Try an improved Quick Assist experience

Reminder: End of servicing for Windows 10, version 21H1

Listen to your favorite Microsoft Tech Community Blog articles, powered by Azure Speech Services!

End user passwordless utopia

Microsoft Teams Premium Experiences and How to Set It Up

Teams Premium preview now available

New Work vertical in Windows Search

Basic Authentication Deprecation in Exchange Online – Time’s Up

Connecting to Azure IoT hub

The main aim of my dive into IoT was to get a remote device talking to Azure. After getting the IoT device connected to WiFi, flashing LEDs, accepting input from a button and capturing temperature data, it was now time to make that dream a reality.

There are different methods of connecting devices to Azure but for my first attempt I decided to use Azure IoT hub. The first step in that process is to login to the Azure portal and create a new IoT hub.


To do this, select the Create menu option in the top left of the Azure IoT hub blade


Once you have selected the Azure subscription and Resource group you’ll need to pick a Name for your Azure IoT hub. This name needs to be unique as a URL will be generated from this. Then select a Region and a Tier. You’ll notice that there is a Free tier, which I have selected for this example (very handy for tests like this).


Next, you can configure your networking. Because my device will just connect to a public Internet connection I selected Public access.


I left the management options as shown above.


The add-ons shown here are not available on the Free tier.


I didn’t need any tags.


I finally get a summary as shown. Note that the cost will be $0 because I am using the Free tier. Select Create to complete the process.


After a few minutes you should be able to see you IoT hub as shown above. Select Devices from the menu on the left.


Now select Add device from the menu on the right as shown above.


Give a the device a Name, and to keep things simple select Symmetric key for the Authentication type as shown. Ensure that the Auto-generate keys is select and that Connect this device to an IoT hub is set to Enable. Select Save to continue.


You should now see the device you just created listed as shown above. Select the name of the device to view it’s properties.


Here you will find the settings for your device. You’ll need to grab at least one Key and the matching Connection string to use when configuring your device.

With all of that information it’s time to head back and set up the device.

I have uploaded the code to get the device connected to Azure IoT hub here:

It is much more extensive that before and I will admit I am not yet 100% sure of what it all does but basically it connects the device to local Wifi then sends telemetry information to Azure IoT hub.

You’ll also need to have the file iot_config.h in the same directory when compiling your code. You can find an example of that here:

that file basically extracts all the unique security information like WiFi password, device keys and IoT Hub URL away from the main code. You’ll need to modify this file to suit your own environment before compiling.

The only other thing you’ll need to do is connect a single LED to pin 5 of the device to act as a diagnostic indicator. It will basically flash when data is sent to Azure IoT hub which gives a nice visual representation of something actually happening on the device.


When you compile the code you’ll also need to ensure all the appropriate libraries are available. Details of each of these is contained in the code.

With the compiled code uploaded to the device you should see the LED light start to flash after a few seconds indicating that data is being sent. If you look at the serial port you should see diagnostic data like so:


If you then look at the Overview page in the Azure IoT Hub you should the diagnostics reporting a number of messages increasing over time like so:


You can also download a tool called the Azure IoT explorer which you will find here:


When you configure this for your IoT hub environment and drill down into the Device then Telemetry, as shown above, should allow to see the actual information being sent.

So there you have it. Once you have set up an Azure IoT hub and added a device to it you can grab the connection details and plug them into the code you use to configure your device. You can also use the Azure IoT Explorer to get more granular details of what your device is doing.

The next challenge is now to get the device working with Azure IoT central.

Adafruit Huzzah Temperature senor


Last project was:

Input from button

Next up now is connecting the DHT20 temperature sensor to the Adafruit Huzzah. The idea is to read data from the sensor and display it via the serial output.

The wiring diagram is shown above and is pretty straight forward. The main thing is to get the pin functions for the sensor. All 4 pins needs to be connected. On the DHT20 pin 1 goes to the 3V output on Huzzah. Next, the DHT20 pin 2 goes to ground on the Huzzah.

The final 2 pins (SCL and SDA) are for serial communications. Thus, DHT20 pin 2 goes to the SCL connection on the Huzzah. Finally, pin 4 from the DHT20 goes to SDA on the Huzzah.

The code is also very straight forward and I found it here:

and my version is at:

To make this work you’ll also need to add the following the library:

Adafruit AHTX0

Once you combine all these elements you can compile the code and upload it to the Huzzah. Now, the Huzzah should produce a serial output that looks like:


which shows the temperature and humidity of the room.

A pretty simple one when it comes to capturing temperature and humidity.

The next challenge will be to getting data in and out of Azure.