ADF connector updates: Azure Database for PostgreSQL, REST and Excel

brianbolger generic in ADF, you can reference the properties in activity output in subsequent activities, e.g. @{activity('Copy').output.xxx}. REST sink doesn't expose specific info now, the request response is not captured there as during one copy activity run multiple requests might be send to write data in batches; error should be there.

Linda_Wang are there any docs or guidance on how to interpret a response from the REST connector sink?

e.g. if we wanted to take some action on a failed response or retrieve a value from the response (such as a new resource Id generated in the case of a POST request) to use later in the pipeline?

Johannes_Vink based on your description it's actually reversed - there is an output size limit for Web activity which feed data back to ADF control flow for subsequent activity to consume, whereas no limit for REST connector as source in copy activity which copy the data to sink data store.

Hm strange. It is not listed in the docs as limitation. I checked how did implement it in the end. REST we could not get working, Web activity did work. The repsonse is picked up in a stored procedure to write to a database. It is a general ADF limitation that the response cannot be too big. In our case it was sufficient.

Writing to REST opens a few scenario's we've left untouched for the moment, will look into that!

Johannes_Vink  I remember there isn't a size limit in REST source. Where do you see the limit? And no limit for REST sink, it writes data in batches.

I there was a limit of 2 MB of downloading data from a REST source. Is there a similar limitation for using REST as a sink?