Tom Harvey

Presumably this is a duplicate of https://github.com/hashicorp/go-azure-sdk/issues/740?

@mbfrahry if you've got them handy, mind posting the Request/Responses?

Ah fun, so it appears to be a Delete LRO masquerading as Regular LRO? We'll likely need to update [the Regular vs Delete LRO logic](https://github.com/hashicorp/go-azure-sdk/blob/c2959a5ca90f488c8891c80d7a9d269a791f45a5/sdk/client/resourcemanager/poller.go#L25) to check if the URI...

@xiaxyi can you provide the HTTP Requests/Responses involved here?

@xiaxyi have you got the full headers for both requests too?

hey @rutgersc Apologies for the delayed reply to this one - just realised this hasn't had a reply. Taking a look at the API response here (and re-running this today)...

@katbyte this [field is marked as Required in the Swagger](https://github.com/Azure/azure-rest-api-specs/blob/d65b5ab4950f0a5fdc7017616fffa6a685b0f3dd/specification/monitor/resource-manager/Microsoft.Insights/preview/2021-07-01-preview/privateLinkScopes_API.json#L928-L936), and since it's the only fields within that payload that's not readonly that looks right to me. Since this field...

@ziyeqf that's a Swagger bug which would need to be fixed - would you mind sending a PR to fix that?

@ziyeqf the Swagger should be defining `x-ms-pageable` to state which field contains the `nextLink`, see here: https://github.com/Azure/autorest/tree/main/docs/extensions#x-ms-pageable As such just updating the API definition should be sufficient there, I don't...

Got it, thanks - in which case yeah this is a bug in the new base layer here where we're relying on the OData value rather than using the value...