Bicep deployment Storage account fileService endpoint not found

Ronny Forberger 45 Reputation points
2023-08-31T01:23:17.37+00:00

I am trying to create a storage account and a NFS share with bicep and Azure DevOps.

Here is my bicep code:

https://pastebin.com/vBb4E1vG

Here is the error message from the management api:

https://pastebin.com/JEEAmLUe

What am I doing wrong? Why is it not finding my resource fileservice on the management api?

Azure Storage Accounts
Azure Storage Accounts
Globally unique resources that provide access to data management services and serve as the parent namespace for the services.
2,109 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. Bhanu Ejjagiri 246 Reputation points Microsoft Employee
    2023-09-05T17:59:43.3966667+00:00

    Hi @Ronny Forberger
    Thanks for contacting Microsoft Q&A Team, and sorry for the delay in responding to this query.

    Few things to check at the below part of the code:

      protocolSettings: {
          smb: {
            authenticationMethods: 'Kerberos'
            channelEncryption: 'AES-256-GCM'
            kerberosTicketEncryption: 'AES-256'
            multichannel: {
              enabled: true
            }
            versions: 'SMB3.0;SMB3.1.1'
          }
    

    Have you tried deploying the account without "Kerbaros"

    Example:

        protocolSettings: {
    
          smb: {}
    
        }
    

    and "multichannel" is supported for "Premium FileStorage" only - Can you set this to "false" and give a try.

    Please help me with the new error message output if you are still facing the issue at the above suggested steps.

    Thanks!

    Regards,

    Bhanu

    0 comments No comments

  2. Ronny Forberger 45 Reputation points
    2023-09-06T08:30:01.54+00:00

    Thanks, I tried to remove the smb: block content, but still the same error:

    ERROR: {"status":"Failed","error":{"code":"DeploymentFailed","target":"/subscriptions/REDACTED/resourceGroups/vmapp/providers/Microsoft.Resources/deployments/storageaccount","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"ResourceDeploymentFailure","target":"/subscriptions/REDACTED/resourceGroups/vmapp/providers/Microsoft.Resources/deployments/myansiblestorageaccount","message":"The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'.","details":[{"code":"DeploymentFailed","target":"/subscriptions/REDACTED/resourceGroups/vmapp/providers/Microsoft.Resources/deployments/myansiblestorageaccount","message":"At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.","details":[{"code":"HttpResourceNotFound","message":"The request url https://management.azure.com/subscriptions/REDACTED/resourcegroups/vmapp/providers/Microsoft.Storage/storageAccounts/ansibleprovision/fileServices/fileservice?api-version=2022-09-01 is not found."}]}]}]}}
    
    

    Any ideas?

    0 comments No comments