Unfortunately not. We are working on this within support ticket with MS.

I have created support request 30962207 and for now I'm waiting for an Engineer.

Ad.1 On-premises. Machine has installed latest OMS Agent.
Ad.2. No, only this linux machine is connected with Azure OMS.
Ad3. No, the problem exists from the beginning when i have created heartbeat alerts.

Right now the only way is to create filter to filtered out this machine but in such case i will not know when server will go down.

I have created Personal Access Token based on provided tutorial on Azure DevOps and use it within Azure DevTest Labs > Repositories.
I am getting error: "GeneralError: GeneralError".

I still thinking that the problem is my permisssions. How can i refresh token at Azure DevOps for repo/project.

This repositories within Azure DevTest Labs will be used by many users.

I cannot directly attach disc to this Server B.

The memory usage now is very high, its about 100GB.

Have you any idea how to control this usage or limit it?

I have tried to empty standby list but it did't help.

This is related to some memory leak or?

There are already few files right now. The same files i can see at RamMap.
We are uploading from serverB big files (few TBs in multiple files). Server has 400GB of memory.
So those processes* took almost all free RAM on the physical server.

@michev could you help me with that? On which forum should i ask this question?

I have add "Deploy" permissions to the group where are the users and they can edit custom properties of the VMs.
There were some changes in SCVMM 2019? Before migration users had only permissions to Deploy (From template only) and they could edit Custom properties.

User profile role for Administrator is administrator. Of course the user role was assigned to the cloud. User is already in this group.
User only have problems with editing Custom Properties within virtual machines in the cloud. The problemm occured after migration, we did not change anything in permissions.

I wrote above what permission user have to this cloud.

This feature will enable syncing PwdLastSet attribute on the user account? I mean if i set 30 days old password on local AD today, and i set 30 days old password on Azure AD few days later what will happen?

When user will be obligate to change password ? Which password policy will be first or there will be synchronization between those policies AD / Azure AD ?