Hi Omar_Abu_Arisheh , WSilveira
We are facing the exact same issue as tiagoacosta198317 .
The FileSystem Connector works as expected when using IP Address as Root path but doesnt work when using FQDN.
Below works as it uses IP Address
"on-prem-filesystem": {
"type": "FileShare",
"accountName": "<Domain>\\<user>",
"shareName": "<share_name>",
"accessKey": "@AppSettingRef(password)",
"mountPath": "\\mounts\\FileSystem",
"state": "NotValidated",
"endpoint": "<IP Address>",
"protocol": "Smb"
}
Below doesnt work when using FQDN. Except the root folder all other fields are same as above.
"on-prem-filesystem": {
"type": "FileShare",
"accountName": "<Domain>\\<user>",
"shareName": "<share_name>",
"accessKey": "@AppSettingRef(password)",
"mountPath": "\\mounts\\FileSystem",
"state": "NotValidated",
"endpoint": "<fqdn here>",
"protocol": "Smb"
}
Our team have confirmed, we can access the fqdn from Kudu Console using the nameresolver command. We use custom dns and its working as expected.
Can you please help.