Added new post and fixed typos on multiple articles

Author: PsCustomObject

_posts/2020-09-21-Exchange-Online-Certificate-Based-Authentication.md

@@ -55,7 +55,7 @@ Once done click on the **Register** button, provision will only take a couple of
   <img src="/assets/images/Azure_Application_Registration_Summary.png"></a>
 </figure>
 
-**Note:** The only field really needed in the *Name* one just be sure to chose a descriptive name that is easy for you to remember.
+**Note:** The only field really needed in the *Name* one just be sure to choose a descriptive name that is easy for you to remember.
 {: .notice--danger}
 
 ### Exchange Online Certificate Based authentication - Grant API Permissions
@@ -115,7 +115,7 @@ Thumbprint                                Subject
 
 Open *Certificate Manager* MMC console and under *Certificates Current User / Personal / Certificates* right-click on the certificate and select *All Tasks / Export*. Just follow the export wizard be sure to select *Do not export private key* and select **CER** as the export format.
 
-In the Azure Portal select *Certificates and Secretes* from the left blade and *Upload certificate* navigating to the path where the certificate has been expoted/stored
+In the Azure Portal select *Certificates and Secretes* from the left blade and *Upload certificate* navigating to the path where the certificate has been exported/stored
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/Azure_Certificate_Upload.png">
@@ -158,7 +158,7 @@ Once configuration is complete you will see a page similar the following
   <img src="/assets/images/Azure_Assignment_Confirmation.png"></a>
 </figure>
 
-where you can review applied configuration and make any required change.
+Where you can review applied configuration and make any required change.
 
 ## Exchange Online Certificate Based authentication - Testing connection
 

_posts/2020-09-25-Azure-Automation-Variables.md

@@ -18,7 +18,7 @@ header:
 
 ## Azure Automation Variables as Shared Resources
 
-Shared Resources in Azure Automation allow us to reuse credentials, modules, schedules, connections, certificates and **variables** which will be will be the main focus of this post.
+Shared Resources in Azure Automation allow us to reuse credentials, modules, schedules, connections, certificates and **variables** which will be will be the main focus of the post.
 
 To better understand the importance of shared resources and *variables in Azure Automation* let's go through a practical example. I have a runbook pulling data from a web service which requires to reference an API secret as part of the process to obtain an authentication token.
 
@@ -131,11 +131,11 @@ As you can see when creating an encrypted variable Value is *omitted* in the out
   <img src="/assets/images/Add_Application.png"></a>
 </figure>
 
-This is the expected behavior as encrypted variables are *secured* with a unique key generated for each **automation account**. It goes alone encrypted variables are more secure in nature but it has to be kept in mind that, once created, azure automation variables have been created **values cannot be seen only updated**.
+This is the expected behaviour as encrypted variables are *secured* with a unique key generated for each **automation account**. It goes alone encrypted variables are more secure in nature but it has to be kept in mind that, once created, azure automation variables have been created **values cannot be seen only updated**.
 
 ### Update and Retrieve Azure Automation variable values
 
-Now that we know how to create azure automation variables let's see how to work with them and update their values. Recall I had a typo in the unencrypted variable, trailing '[' character, let's fix that from the console
+Now that we know how to create azure automation variables lets see how to work with them and update their values. Recall I had a typo in the unencrypted variable, trailing '[' character, let's fix that from the console
 
 <figure>
   <a href="https://pscustomobject.github.io//assets/images/Azure_Automation_Update_Variable_Value.png">
@@ -195,7 +195,7 @@ LastModifiedTime      : 26.09.2020 19:14:46 +02:00
 Description
 ```
 
-## Getting Variable value
+## Getting Variable Values
 
 Up to this point we've seen how to create and update Azure Automation variables, let's explore how to get values for configured variables.
 *Az* module makes available a cmdlet for the purpose
@@ -216,7 +216,7 @@ Description           : Fixed typo in value
 **Note:** Omitting the *-Name* parameter will return all configured variables
 {: .notice--primary}
 
-As I mentioned it is not possible to retrieve values for encrypted variables as they're available within the runbook at runtime via the **Get-AutomationVariable** cmdlet. Using the *Test Encrypted Variable* as example I've created a small script that will show this behavior
+As I mentioned it is not possible to retrieve values for encrypted variables as they're available within the runbook at runtime via the **Get-AutomationVariable** cmdlet. Using the *Test Encrypted Variable* as example I've created a small script that will show this behaviour
 
 ```powershell
 $encryptedVariableValue = Get-AutomationVariable -Name 'Test Encrypted Variable'

_posts/2021-05-02-Write-Raspberry-Image-Command-Line.md

@@ -16,7 +16,7 @@ header:
 
 I am in the process of rebuilding my *Docker/Kubernetes* portable cluster which I build using a couple of RaspberryPi 4 and as part of this I needed to *reflash* the various SD cards where operating system for each node is installed.
 
-Usually [Balena Etcher](https://www.balena.io/etcher/) is my go-to tool for such endeavors but being in a rush and not easy way to download the tool on my Linux box I simply used the good old command line, here is how this is done.
+Usually [Balena Etcher](https://www.balena.io/etcher/) is my go-to tool for such endeavours but being in a rush and not easy way to download the tool on my Linux box I simply used the good old command line, here is how this is done.
 
 First of all we need to locate the device mapped to our SD card, in my case I'm using a microSD to USB adapter, which can be done with the following command:
 

_posts/2021-05-28-Get-Current-User-UPN.md

@@ -48,6 +48,6 @@ This can easily be achieved with the following command:
 ([ADSI]"LDAP://<SID=$([System.Security.Principal.WindowsIdentity]::GetCurrent().User.Value)>").UserPrincipalName
 ```
 
-This command,despite not as user friendly as the other commands, will return the full UPN of the user for example **PsCustomObject@domain.com**.
+This command, despite not as user friendly as the other commands, will return the full UPN of the user for example **PsCustomObject@domain.com**.
 
 I encourage you to explore the other available methods and properties of the *[System.Security.Principal.WindowsIdentity]* [class](https://docs.microsoft.com/en-us/dotnet/api/system.security.principal.windowsidentity?view=net-5.0) as it can be really handy when trying to get details about the current user.

_posts/2022-01-25-annot bind argument to parameter-Token-Expiry.md

@@ -0,0 +1,57 @@
+---
+title: "Cannot bind argument to parameter TokenExpiryTime because it is null - Error Message"
+excerpt: "When opening a PowerShell session to both on-prem and Exchange online in the same window cannot bing argument to parameter TokenExpiryTime because is null error message could be displayed. Let's explore how to solve this."
+categories:
+  - PowerShell
+  - Exchange
+  - Office 365
+
+tags:
+  - PowerShell
+  - Office365
+  - Exchange
+
+toc: true
+header:
+  teaser: "/assets/images/PowerShell_Logo.png"
+---
+
+## Exchange Online Certificate Based authentication
+
+Microsoft is, *finally*, disabling **basic authentication** (read username and password) in Exchange Online in favour of **Certificate Based authentication**.
+
+Once this change is fully implemented, around mid February at least for some tenants, connecting via username and passwords to Exchange Online will not be possible anymore. 
+
+You can read my article on how to implement *Certificate Based authentication*  for Exchange Online [here](https://pscustomobject.github.io/powershell/office365/exchange/Exchange-Online-Certificate-Based-Authentication/).
+
+As a result of this change I started updating one of our automations, responsible for the whole lifecycle of our mailboxes, to ditch old credential objects in favour of the more secure Certificate Authentication. 
+
+This is when I encountered the *‌cannot bind argument to parameter 'token expiry time' because it is null.* error message.
+
+## Multiple PowerShell Exchange Sessions
+
+When operating an hybrid environment it is pretty common to open, in the same window/session, a PowerShell connection to both Exchange on-prem and Exchange online. 
+
+This is required as part of the configuration, usually creation of the mailbox, takes place in on-prem for example via the *New-RemoteMailbox* cmdlet while other parts of the configuration are performed directly online.
+
+This morning while debugging my workflow I’ve noticed that while  trying to retrieve mailbox information from the on-prem server an exception was being thrown
+
+```powershell
+# Cmdlet I was running
+Get-RemoteMailbox -Identity $userUpn
+
+# Part of the exception message
+Cannot bind argument to parameter 'token expiry time' because it is null.
+```
+
+It took me quite a bit to figure this out as no exception during the connection phase was being thrown by either module.
+
+When I was about to give up and open a ticket with Microsoft, which is usually as helpful as freezer in the North Pole, I discovered by chance that opening connection to Exchange Online **first** and **only afterwards** to the Exchange on-prem was working as intended, allowing me to interact with both the Online service and my local Exchange. 
+ 
+**Note:** I have experienced/tested this with version 2.0.4 and 2.0.5 of Exchange Online PowerShell module but other versions could be affected as well.
+{: .notice—warning}
+
+I did not dig deep into the root cause of the issue but plan to do this tomorrow and already sent my feedback to exocmdletpreview {at} service {fullstop} microsoft {fullstop} com but I doubt I will hear anything from that channel. I plan to open a ticket anyhow to at least have an official statement on this. 
+
+As soon as I have any news I will update the post until then I hope you can find the information useful.
+