I had a task to migrate one of our standard service buses to premium, and when I tried to do so, I faced a very odd error: during the sync step, when the settings\keys\topics are syncing up from the old bus to a new one, they just stuck on 1 entity remaining (total 1) and haven’t moved at all.
Continue readingWe had this odd issue when, after installing the ESU keys, the servers were still unable to receive updates and gave us back a failed installation.
Continue readingWe received an inquiry from PlatOps regarding potential integration with our Exchange online. Due to our strict security protocols that prohibit non-secure authentication methods, I took the initiative to develop a script that utilizes MS Graph and Modern Auth for sending emails in a secure manner.
Continue readingIt might not be a common issue for everyone, but I was travelling a lot in my life, and at some point when I was in New Zealand – I happened to create an Azure account to use with my MSDN offer, and it was created in NZD. It was fine until I moved to Ireland, and now, to keep the books tidy, I wanted to change my currency to EUR.
Microsoft docos and support stand firm that this is not possible to change your billing profile residency. However, looking under the hood, it appears to be possible with some digging in and PowerShell magic.
Once I was working on migrating Azure AD Connect from one server to another. After the migration, no matter that the account had rights on the SDadmin folder, some accounts failed to be updated with an insufficient rights error.
After some digging, I found that some accounts historically have adminCount set to 1 and inheritance turned off, so to fix that, I used the following script below:
Continue readingBy the standard way of imputing the new key into the activation form, you’ll get an error that this edition could not be upgraded. However, the MS guide stands for if you’d like to activate your Azure configuration server you’d need to do that through DISM:
And the command is simple as that:
Continue readingDue to some reasons, I had a task to install JunOS space on our Azure tenant, and that appeared to be not that straightforward as I thought. But definitely fun.
Continue readingWhile setting up the Xero connector I faced an issue when after 30 minutes connector stopped working and return an error 400:
Type=Microsoft.DataTransfer.Common.Shared.HybridDeliveryException,Message=ERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400\r\nERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400,Source=Microsoft.DataTransfer.Runtime.GenericOdbcConnectors,''Type=System.Data.Odbc.OdbcException,Message=ERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400\r\nERROR [HY000] [Microsoft][Xero] (61) API Connection Failed. Bad Request. HTTP Response code: 400,Source=,'",