Same CSR with different signature using sha256WithRSAEncryption - encryption

Question

The bounty expires in 19 hours. Answers to this question are eligible for a +50 reputation bounty.
XWIKO wants to draw more attention to this question:
Explain why using the same private key and sha256 can yield different results from Azure KeyVault and OpenSSL
I have downloaded a CSR from Azure Key Vault and wanted to recreate that CSR with openSSL commands.
Reason is we might want to create that CSR from scripts without having an Azure KeyVault.
My context:
I Created a CSR in Azure KeyVault
I have a retrieved the private key that the KeyVault used to create the CSR.
I inspected the KeyVault generated CSR using openssl req -text -noout -verify -in csr.csr
I Created my own CSR using OpenSSL And made sure all the subject information and Requested Extensions are the same as the KeyVault one.
When inspecting the newly created CSR (using above command) and the one generated by Azure KeyVault, they are identical (e.g. same modulus, same request extensions, same subject) except for the signature.
My question:
Are there components in a CSR that are not inspected using above command that can explain why the signatures are different while the rest is the same? Or is it because it is generated on a different machine? Or can it be they (KeyVault and OpenSSL) used different algorithms for sha256WithRSAEncryption which is not viewable with above inspection command? I'm trying to understand.
Version: 1 (0x0)
Subject: <<obf>>
Subject Public Key Info:
Public Key Algorithm: rsaEncryption
RSA Public-Key: (2048 bit)
Modulus:
<<obf>>
Exponent: 65537 (0x10001)
Attributes:
Requested Extensions:
X509v3 Key Usage: critical
Digital Signature, Key Encipherment
X509v3 Extended Key Usage:
TLS Web Server Authentication, TLS Web Client Authentication
X509v3 Subject Alternative Name:
DNS:<<obf>>
X509v3 Basic Constraints:
CA:FALSE
Signature Algorithm: sha256WithRSAEncryption
<<obf>>