AzureArc: Resource name in namespace 'Microsoft.HybridCompute' cannot contain more than 54 characters.

Dmitriy Kolesnikov 11

Using the onboarding script, I tried to onboard a virtual machine from GCP to Azure Arc. The VM (linux RedHAT) reports its hostname as "<servername>.<region>.c.<projectname>.internal" and I get the following error from my script:

"FATAL invalid resource name 'feprodsssrhl01.us-central1-a.c.fluence-services.internal'. Resource name can only contain alphanumeric characters, '-' , '_' or '.'. Resource name in namespace 'Microsoft.HybridCompute' cannot contain more than 54 characters. "

Is there a workaround to onboard that VM without changing its name?

Pranay Reddy Madireddy 2,075 Reputation points Microsoft Vendor

2025-02-05T20:12:08.1866667+00:00
Hi Dmitriy Kolesnikov

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

Instead of using the onboarding script, you can manually install the Azure Connected Machine agent by following these steps:

Download the AzureConnectedMachineAgent.msi file to your VM.

Run the installer manually.

After installation, configure the agent by running the following command in the command prompt:

"%ProgramFiles%\AzureConnectedMachineAgent\azcmagent.exe" connect --resource-group "<resourceGroupName>" --tenant-id "<tenantID>" --location "<regionName>" --subscription-id "<subscriptionID>"

During this process, you will be asked to authenticate through a web link, just like the onboarding script does.

If possible, create a new resource in Azure with a valid name that follows Azure's naming rules. This may include setting up a new VM or resource group with a compliant name and moving your application or data to it. Make sure the name only uses letters, numbers, hyphens, periods, and underscores, and is no longer than 54 characters.

If you can't change the hostname, you can use an alias or a different identifier for your VM in Azure that follows the naming rules. This will help keep things clear, but you'll need to manage it separately in your documentation and operations.

Check if there are any Azure policies that enforce naming rules or other restrictions that could interfere with onboarding. If so, you may need to change them.

https://learn.microsoft.com/en-us/azure/azure-arc/servers/deployment-options
https://learn.microsoft.com/en-us/azure/azure-arc/vmware-vsphere/azure-arc-agent

If you have any further queries, do let us know.

If the answer is helpful, please and "Upvote it".
Dmitriy Kolesnikov 11 Reputation points

2025-02-05T20:37:39.38+00:00

Your suggestion is relevant to Windows resources, but I have a problem with the Linux server.

Also, I can't "create a new resource in Azure" because that resource is hosted on the Google Cloud Platform.
Pranay Reddy Madireddy 2,075 Reputation points Microsoft Vendor

2025-02-06T15:28:27.5766667+00:00
Hi Dmitriy Kolesnikov

Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

To manually install the Azure Arc agent on your Linux VM, follow these steps:

Use curl or wget to download the Azure Arc agent.

Install it by following the Linux-specific instructions, which may include using a package manager such as yum or apt-get.

To connect the VM to Azure Arc, run the command below, ensuring you specify a compliant name using the --display-name parameter:

sudo azcmagent connect --resource-group "<resourceGroupName>" --tenant-id "<tenantID>" --location "<regionName>" --subscription-id "<subscriptionID>" --display-name "<compliantName>"

This allows you to use a compliant name for Azure without changing the original hostname.

You can add entries to the hosts file or set up DNS to link the Azure resource name to the actual hostname. This way, network operations stay consistent without needing to change the hostname.

Check that there are no Azure policies blocking resource names or other settings. If needed, temporarily change these policies to allow the onboarding process to go smoothly.

https://azurearcjumpstart.com/azure_arc_jumpstart/azure_arc_servers/general/onboard_server_linux
https://petri.com/install-azure-arc-agent-on-linux/

If you have any further queries, do let us know.

If the answer is helpful, please and "Upvote it".
Dmitriy Kolesnikov 11 Reputation points

2025-02-06T15:55:17.4766667+00:00

I resolved it by adjusting my script, adding the "resourcename" parameter defined as first 32 symbols from the "hostname" command output value.

1 answer

Pranay Reddy Madireddy 2,075 Reputation points Microsoft Vendor

2025-02-06T15:59:35.8033333+00:00

Hi @Dmitriy Kolesnikov

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer.

Issue:
AzureArc: Resource name in namespace 'Microsoft.HybridCompute' cannot contain more than 54 characters.

Solution:
I resolved it by adjusting my script, adding the "resourcename" parameter defined as first 32 symbols from the "hostname" command output value.

If you have any other questions or are still running into more issues, please let me know. Thank you again for your time and patience throughout this issue.

Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

AzureArc: Resource name in namespace 'Microsoft.HybridCompute' cannot contain more than 54 characters.

1 answer

Your answer