Merge pull request #292 from aspose-pdf/PDFNET_57973_Converting_Documents_Microsoft_Azure

Converting documents in Microsoft Azure (PDFNET-57973)

Author: alevsh

net/advanced-operations/_index.md

@@ -21,7 +21,7 @@ sitemap:
         "name":"Anastasiia Holub",
         "givenName": "Anastasiia",
         "familyName": "Holub",
-        "url":"https://www.linkedin.com/in/anastasiia-holub-750430225/"
+        
     },
     "genre": "pdf document generation",
     "keywords": "pdf, c#, advanced operations in pdf, create pdf, delete pdf, manipulate pdf",

net/other-programming-languages/microsoft-azure/_index.md

@@ -0,0 +1,31 @@
+---
+title: Converting Documents in Microsoft Azure
+linktitle: Converting Documents in Microsoft Azure
+type: docs
+weight: 110
+url: /net/microsoft-azure/
+lastmod: "2024-10-25"
+sitemap:
+    changefreq: "weekly"
+    priority: 0.5
+---
+
+This article provides detailed step-by-step instructions for converting PDF documents in Microsoft Azure using Aspose.PDF for .NET.
+
+## Prerequisites
+* Azure Account: You need an Azure subscription, create a free account before begin.
+* Visual Studio 2022 Community Edition with installed Azure development or Visual Studio Code.
+
+## Restrictions
+When you are working with Aspose.PDF for .NET in an Azure environment, you generally need to configure your Azure service for Full Trust to use all the capabilities of Aspose.PDF. This is especially true for more complex operations like PDF to image conversions, font embedding, or file format conversions, which require unrestricted access to system resources.
+
+Aspose.PDF performs certain operations that may require access to:
+
+* System resources such as fonts and images.
+* Temporary storage for processing files.
+* Memory management that might need elevated permissions to operate efficiently.
+
+Azure environments, particularly App Service and Azure Functions, run in a partial trust environment by default. Partial trust restricts certain resources that libraries like Aspose.PDF rely on, which can lead to issues or errors in document processing.
+
+## Set license
+It is recommended to use the license file as an embedded resource in your application. If you don’t want to embed the license file in your project, you can store it in Azure Blob Storage and load it from there.