Forum Widgets
Latest Discussions
Can't access http context user claims in Azure Function
Background: Create an Azure Function (.NET Core & C#) that will be consumed in a SPO App. We created an Entra App Registration for the Azure Function and added App Roles for this App Registration where the App Role is using “Users/Group”, but not “Application”. Issue: In the SPO App (deployed in SPO Page), we can see the user claim and App Registration’s - App Role in the context of the user that’s hitting the SPO Page (thru Authorization header), however, in the Azure Function code the req.HttpContext.User.Claims object is empty. So what is required or missing from a configuration perspective either in the Azure Function or App Registration to make this work?
LogicApps for AZURE VM with SharePoint farm
Hello I was wondering if it is possible to access with LogicApps a SharePoint farm in a AZURE VM. I am a developer and like to use my MSDN Subscription to access Logic Apps for using SharePoint test environment on a VM in AZURE. If it is possible, how I can do that, what are the steps, like: (1) App Registration (2) Configure an endpoint to VM and SharePoint (3) etc... Thanks in advance for any suggestion or help. Kind regards Michael
Azure Function App Http Javascript render simple html file to replicate jsrsasign sign certificate
Good day, Please Help. 1. In PowerBI im trying to render the javascript sign certificate of jsrsasign, i only got it working via an html file. So im trying to read the html file, simple hello to start of with. Am i better going directly to do the jsrsasign? 2. Locally on VS i got the simple function to return Hello Azure, but trying to read the simple html file executes no error but if i copy in postman i just get a 401 no content found, im not sure how further to debug as in VS i get Ok status, Nothing in Console? Anybody have an example or links plz? const { app } = require('@azure/functions'); const fs = require('fs'); const path = require('path'); app.http('IC5', { methods: ['GET', 'POST'], authLevel: 'anonymous', handler: async (request, context) => { context.log(`Http function processed request for url "${request.url}"`); // const name = request.query.get('name') || await request.text() || 'world'; // return { body: `Hello, ${name}!` }; //var res = { //body: "", //headers: { //"Content-Type": "text/html" //} //}; // readFile = require('../SharedCode/readFile.js'); //filepath = __dirname + '/test3.html'; //fs = require('fs'); //await fs.readFile(filepath,function(error,content){ fs.readFile(path.resolve('./test3.html'), 'UTF-8', (err, htmlContent) => { context.res = { status: 200, headers: { 'Content-Type': 'text/html' }, body: htmlContent } }) // if (request.query.name || (request.body && request.body.name)) { // res.body = "<h1>Hello " + (request.query.name || request.body.name) + "</h1>"; //} else { //fs.readFile(path.resolve(__dirname,'test3.html'), 'UTF-8', (err, htmlContent) => { //res.body= htmlContent; //context.res = res; //}); // } } }); //TEST IN POSTMAN: http://localhost:7071/api/IC5?name=hurry
Unable to trigger function app while using managed identity for the storage account connection
I am trying to create an Azure Function of BlobTrigger type, which needs to be triggered on dropping files in the storage account say filessa. Due to policy restriction the storage account cannot use shared access key. I am unable to trigger the function app dropping a file into a container. I see intermittently an error in the function app logs No valid combination of account information found. assembly : Azure.Storage.Blobs, Version=12.23.0.0, Culture=neutral, PublicKeyToken=9279e12e44c8 method : Azure.Storage.StorageConnectionString+<>c.<Parse>b__67_0 outerType : Microsoft.Azure.WebJobs.Host.Indexers.FunctionIndexingException outerMessage: Error indexing method 'Functions.SPAREventGridBlobTrigger' innermostMessage: No valid combination of account information found. I am referring to Configuring Azure Blob Trigger Identity Based Connection and have created the environment settings and assigned required roles to storage accounts (function App's storage account, say fnsa and the storage account which is used to upload the file to trigger the function app, filessa) as mentioned in this article. This is my simple code [Function(nameof(SPAREventGridBlobTrigger))] public async Task Run([BlobTrigger("samples-workitems/{name}", Source = BlobTriggerSource.EventGrid, Connection = "filessa_STORAGE")] Stream stream, string name) { using var blobStreamReader = new StreamReader(stream); var content = await blobStreamReader.ReadToEndAsync(); Console.WriteLine("Hello from Jey Jey Jey"); _logger.LogInformation($"C# Blob Trigger (using Event Grid) processed blob\n Name: {name} \n Data: {content}"); } I have assigned roles to the storage account filessa Storage Blob Data Owner and Storage Queue Data Contributor for the Azure Function identity. and assigned roles to the storage account fnsa Storage Blob Data Contributor for the Azure Function identity. (Actually I ended up adding many other roles like Storage Account Contributor, Storage Blob Data Reader and similar too to both storage accounts) Please advice me to on the items to be added in the environment settings. 1. the name and value of the connection of the storage account, filessa 2. the name and value of the connection of the storage account, fnsa 3. other items that needs to be mandatorily added to make it work I have tried added items like AzureWebJobsStorage, AzureWebJobsStorage__accountName, AzureWebJobsStorage__blobServiceUri, ..., AzureWebJobsfilessa_STORAGE, filessa_STORAGE. I have also referred to this microsoft documentation Tutorial: Trigger Azure Functions on blob containers using an event subscription ; tried adding the EventSubscription in the storage account filessa. The webhook https://FA-SPAREG-FA.azurewebsites.net/runtime/webhooks/blobs?functionName=Host.Functions.SPAREventGridBlobTrigger&code=_MPRFuo9sdEg== in Postman with POST returned back error Please help me with all the required environment settings to be added in the function app in Azure and any other suggestion or steps I have missed here to make this work.Azure App that was working with MS SQL Server database now not working with Azure SQL Database
We had a web page app in Azure that ran a form for data retrieval. When we removed the SQL server and moved the database to Azure SQL, the app no longer works. We tried the ADO.NET (SQL authentication) connection string from the database page, but the app is not working. The error we are getting is "The page cannot be displayed because an internal server error has occurred." We are having trouble trying to figure out if we have a connection issue to the database or this is a problem with the app itself. Any suggestions would be appreciated please.Printing from RDP session not working on macOS Sequoia 15.4
Hi, I just wanted to let you know that printing from a Microsoft Remote Desktop Beta session using a redirected printer does not appear to work on macOS Sequoia. The issue has been present since version 15.1.1 and continues in the latest 15.4 update. I’ve tested several versions of Microsoft Remote Desktop Beta, including 10.9.3, 10.7.5, 10.6.8, and others. In all of them, the printer appears inside the RDP session, and the print job briefly enters the queue before disappearing without printing. Additionally, in the new Windows App, as well as in Microsoft Remote Desktop Beta starting with version 10.9.4 (2160), no printers appear at all inside the RDP session — printer redirection seems to be completely absent. For comparison, on a MacBook Pro 13" (2017) running macOS Ventura 13.7.2 with Microsoft Remote Desktop 10.9.10 (2327), everything works as expected. Please let me know if this is a known issue or if a workaround is available.
Issue with Mounting Persistent Volume in MongoDB Container on Azure Container Apps
Hi, I'm running a MongoDB container (mongo:latest) on Azure Container Apps, but I'm facing an issue when mounting a persistent volume for MongoDB data. The container works fine before mounting the volume, but fails to start once the volume is mounted. Here is the summary of the issues found in the container logs: File Exists Errors: The error message __posix_open_file:924:/data/db/WiredTiger.wt: handle-open: open, along with the error code 17 (File exists), suggests that MongoDB is unable to open the WiredTiger.wt file because it already exists. Operation Not Permitted: The error __posix_open_file:924:/data/db/WiredTiger.wt: handle-open: open, along with the error code 1 (Operation not permitted), indicates that MongoDB does not have permission to open the WiredTiger.wt file. Renaming of Unexpected Files: The logs show that MongoDB is attempting to rename unexpected files (WiredTiger.wt to WiredTiger.wt.56, WiredTiger.wt.57, etc.) when it encounters issues. WiredTiger Startup Failure: The message Failed to start up WiredTiger under any compatibility version. This may be due to an unsupported upgrade or downgrade. indicates that MongoDB is unable to start the WiredTiger storage engine. Fatal Assertion: The error Fatal assertion followed by the message Terminating. Reason: 1: Operation not permitted means that MongoDB has encountered a critical error and is terminating. Steps Taken to Mount the Volume: Created a Storage Account and added a file share (Access tier: Transaction optimized). In the Container Apps Environment, added Azure File (SMB) and specified: Storage Account Name Storage Account Key File Share Name Access Mode: Read/Write In MongoDB Container App, added a volume with: Volume type: Azure File Volume File Share Name: Chosen from step 2 In MongoDB Container App, under the Containers section, added a volume mount: Volume Name: Specified volume from step 3 Mount Path: /data/db What I Have Tried: In my MongoDB Container App, under the Containers section, on the Properties tab, fields Command override and Arguments override I tried to change permissions as following Command override = /bin/bash Arguments override = chown -R 999:999 /data/db && chmod -R 777 /data/db && exec /usr/bin/mongod I also tried Arguments override = -c "chown -R 999:999 /data/db && chmod -R 777 /data/db && exec /usr/bin/mongod" and Command override = /bin/bash -c "chown -R 999:999 /data/db && chmod -R 777 /data/db && exec /usr/bin/mongod" Mounting volume to another directory /data/mongodb, then changing permissions for that directory and making this directory as working folder for MongoDB. az containerapp update \ --name mongodb-container-app \ --resource-group rg-container-apps-4890 \ --command "/bin/bash -c 'mkdir -p /data/mongodb && chown -R mongodb:mongodb /data/mongodb && /usr/bin/mongod --bind_ip_all --dbpath /data/mongodb'" Despite these efforts, I still encounter the same errors. Could anyone suggest what might be wrong with my setup or provide any guidance on resolving this issue?Authentication deadlock
I got a Microsoft 365 developer account and a sandbox as well. Many months ago it asked me to configure 2FA which I did using Microsoft Authenticator app on Android. I also had other 2FA setup on the same device for some work accounts. Later, somehow my sandbox account got deleted or overwritten from the authenticator app on my phone. I haven't been able to login to my Office 365 sandbox ever since. Ever flow I try asks me to use the authenticator on application. But the problem is that access to authenticator for 2FA was lost due to an app error. Our company's IT department said they can't do anything about it. I tried to delete the profile but when I created it Microsoft gave back the same sandbox which was already not working. My employer spends a good deal of money on Microsoft and it's very upsetting to get such a treatment from Microsoft. This account is needed for my office work. Help appreciated.