Microsoft Azure Storage Table Writer Parameters

About Web Connections

Connections store authentication information.

For general information about web connections, please see Using Web Connections.

For information about managing web services (including authorization credentials such as Client Id and Client Secret), please see Managing Web Services.

Connection

From the Connection parameter in a web service format, you can do one of the following:

  • Select an existing previously defined connection. For information, see the section Reusing a Web Connection in Using Web Connections.
  • Select Add Web Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users.

Microsoft Azure Storage Connection

Select an existing Microsoft Azure Storage connection, or Add Web Connection....

Add Microsoft Azure Storage Connection

To define a new connection from the Connection parameter in a Microsoft Azure Storage Table format, see the topic Microsoft Azure Storage Table: Add Web Connection.

Advanced

Specifies which SQL operations will be performed by default by this writer. This default writer-level value can be overwritten at the feature type or table level.

  • Insert – Allows for only Insert operations.
  • Update and Delete – These writer modes can be overwritten at the feature type level.
  • Yes (default) – Ensures that a URL's digital certificate is valid (signed by a trusted certificate authority), trusted, and belongs to the domain to which you are connecting.
  • No – Verification will not be performed (that is, there is no verification that the URL’s certificate is valid or trusted).
Warning  Setting this parameter to No could allow the HTTP request/response to be intercepted.

How FME Processes Multiple Verification Parameters in a Workspace

FME evaluates the setting at the workspace component level. If a reader/writer or web connection has the Verify HTTPS Certificate(s) parameter set to Yes, and an HTTPCaller transformer has the Verify HTTPS Certificate(s) parameter set to No, then the reader will verify certificates for its data requests, but the transformer will not verify certificates for its own requests.

FME does not combine multiple verification parameters — it uses the parameter local to the reader/writer, transformer, or web connection that is making the web call.

It is good practice to ensure that all Verify HTTPS Certificate(s) parameters in a workspace are set to Yes.

Note  
  • On MacOS, requests to some servers will not work unless this parameter is set to Yes.
  • The value of the Verify HTTPS Certificate parameter takes priority over the value of the Verify SSL Certificates parameter, which may be defined by the Web Connection used with this format.