Azure or M365 configuration changes are not reflected immediately to end users

Case



There are various cases in Azure resource configuration and in Microsoft 365 resource provisioning or configuration in which a configuration change made by an administrator cloud-side is not reflected immediately at user-side.



Solution



This behavior in most cases is by design but the end-users should be aware of ways to "reset" their local client state to reflect the cloud-side configuration changes.



One possible reason why a new Azure or M365 resource provisioning or configuration action is not reflected immediately to the clients is because it normally takes some time for the configuration change to replicate in all underlying components which comprise the configuration in question. For example in an Azure VM scale set or in an Azure Web App with multiple instances running simultaneously, replicating the configuration changes to all underlying resources may take some time. This is especially true if the Azure resource is setup in a multi-region design, in which case configuration changes need to be replicated between regions. This replication time is usually not higher than 1 hour. However in certain cases it make take up to 8 hours or longer. If this is the case, then you will most likely need to open an Azure or Microsoft 365 technical support ticket, so that the operations team can carry out checks in the respective Azure service back ends.



A second factor to take into account is that for the configuration and management of various Azure and Microsoft 365 resources, different APIs can be used. One great example is the case of the Microsoft 365 portal vs the Exchange Online portal for managing Azure AD users and Exchange Online mailboxes. Configuration changes are reflected almost immediately in the Exchange Online admin portal while they may take some time to be reflected in the Microsoft 365 portal.



Microsoft 365 admin portal

Exchange Online admin portal

Some of the admin interfaces utilize Microsoft Graph API in the back end while others utilize the Office365 REST API (to be deprecated). In the case of Azure, administrators can always use the Azure Resource Explorer tool to verify the Azure resource state after any configuration change.



A third factor why a configuration change in an Azure resource may take longer than expected to complete is because a third party application does not handle the Azure resource configuration change in such as a way so as to avoid restarting the application instances themselves. One typical scenario in which this can happen is if a .NET app hosted on Azure does not implement the
https://stefanos.cloud/kb/azure-or-m365-configuration-changes-are-not-reflected-immediately-to-end-users/

Comments

Post a Comment

Popular posts from this blog

Acronis Cyber Protect 15 virtual machine backup not working when using shared mode virtual disks vhds

Image
Case When you apply and run an Acronis Cyber Protect backup against a virtual machine which is part of a guest cluster which makes use of virtual disk shared files of type .vhds (VHD Set), you run across the following error. Activity succeeded with warnings. Activity 'Preparing for backup of virtual machine' succeeded with the following warning 'Windows error: (0xC05CFF0A). The requested operation cannot be performed on the virtual disk as it is currently used in shared mode. Or the error may state something along the lines of: "Failed to open virtual disk file '.vhds'. Unknown format of the virtual disk." The same error as above can occur in virtual machine backup of virtual machines which include a .vdhx shared disk. Solution The above error is by design when you are attempting a virtual machine backup to virtual machine which does not have an Acronis backup agent installed, as per https://kb.acronis.com/content/68573 . According to Acronis, as of July 2
Read more

How to perform hardware health checks in Windows

Image
Case You need to perform an overall hardware health check in a Windows machine, running either a Windows client or a Windows Server operating system. This article provides guidance on the steps to carry out to perform hardware health checks in Windows. Solution Carry out the steps below. - Thoroughly check all Windows event logs (Application, System, Security) for any warnings or errors which may be related to issues you are experiencing with your Windows machine. - Check the device management mmc console by running devmgmt.msc. Ensure that you choose to show all hidden devices from the View menu. If you notice any exclamation marks next to any device, you will need to re-install its driver from the respective manufacturer to ensure that there afterwards no warnings in the device management console. - Check the health of all your disks , either HDD or SSD. Follow instructions in the following KB article for steps to follow to check your disk health: https://stefanos.cloud/kb/how-to-ch
Read more

How to resolve Group Policy error codes 8007071a and 800706ba

Image
Case You are running "Group Policy Update" on an OU inside the Group Policy Management Console in Active Directory but you are receiving RPC errors from your servers or domain-joined workstations, as shown in the example below. After a Group Policy Update, you come across Group Policy error codes 8007071a and 800706ba. This means that the local Windows Firewall is not configured properly to allow Group Policy (GPO) traffic. GPO traffic an be either remote GPO update or remote GP Resultant Set of Policy (RSOP) operations. Solution Option 1 Run gpedit.msc and create a new local group policy object which implements the following policies under Local Computer Policy --> Computer Configuration --> Windows Settings --> Security Settings --> Windows Defender Firewall --> Inbound Rules : The full configuration is shown below. After the above local group policies are configured on each domain server and workstation, you can start applying group policy objects to the dom
Read more