Azure SQL MI: CLR Assemblies are marked as SAFE or EXTERNAL_ACCESS are considered UNSAFE

Hi @Santhamoorthy M ,

When upgrading a server, the feature is turned off for backward compatibility in SQL Server, 'CLR strict security' will be set to 0, but it is not recommended.

running the following command:

SELECT * FROM sys.configurations WHERE name LIKE 'clr strict security';  

the value of 1 means that the CLR strict security is switched on

To set the value to 1:

EXEC sp_configure 'clr strict security',1;  
GO  
RECONFIGURE;  
GO  

you can add the CLR strict security feature to Microsoft SQL Server from KB4018930

Additional:
https://stackoverflow.com/questions/44083098/clr-strict-security-on-sql-server-2017#:~:text=Beginning%20with%20SQL%20Server%202017%2C%20an%20sp_configure%20option,EXTERNAL_ACCESS%20assemblies%20as%20if%20they%20were%20marked%20UNSAFE.
https://www.sqlshack.com/impact-clr-strict-security-configuration-setting-sql-server-2017/

-------------

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.