Securing sensitive information like passwords, tokens, and license information is a very important aspect of data management. In Business Central, ensuring data security can be achieved through Isolated Storage. In this blog post, we’ll guide you through a practical example of password management, showcasing how Isolated Storage adds an extra layer of protection.
Today I will show you how you can perform multiple operation on any file in Business central by accessing of Azure blob storage.
I going to work on some image file, where I will store those files into blob storage and after reading that file move that file into another folder and delete from the source folder.
“Isolated storage” is a data storage method that allows you to isolate data between different extensions, even within the same extension.
It is possible to archive key-value pairs in an isolated archive and define the scope of the archived data (through an access level called “Data Scope“).
Business Central allows us to perform Isolated Storage, which is extremely useful if, for example, we want to store Passwords, Tokes, and Secrets without having to resort to Tables.
A couple of weeks ago I made a post on How to Test Outh2, through the native Business Central codeunit, but every time we closed the window, the token disappeared. So I came up with a good example idea, adding Isolate Storage to mitigate this issue.