Azure API Management for Authenticating Internal Tools

%3CLINGO-SUB%20id%3D%22lingo-sub-809722%22%20slang%3D%22en-US%22%3EAzure%20API%20Management%20for%20Authenticating%20Internal%20Tools%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-809722%22%20slang%3D%22en-US%22%3E%3CP%3ETrying%20to%20wrap%20my%20head%20around%20the%20%22best%22%20way%20to%20authenticate%20some%20internal%20tooling%20for%20our%20organization%20that%20integrates%20nicely%20with%20all%20the%20Microsoft%20365%20resources.%26nbsp%3B%20I'd%20like%20to%20be%20able%20to%20transparently%20utilize%20our%20existing%20Azure%20AD%20to%20authenticate%20these%20client%20side%20interfaces%20(teams%20apps%2C%20sharepoint%20web%20parts%2C%20generic%20web%20apps%2Fdesktop%20apps%2C%20etc)%20when%20they%20call%20back-end%20web%20APIs%20that%20will%20exist.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20trying%20to%20stay%20fairly%20low%20cost%2C%20as%20these%20are%20going%20to%20mostly%20be%20tiny%20apps%20e.g.%20some%20mild%20automations%20and%20information%20surfacing.%26nbsp%3B%20Right%20now%20I%20am%20looking%20at%20using%20Azure%20Functions%20%2B%20a%20storage%20account%20using%20the%20Tables%20storage%20API%20%2B%20API%20management%20to%20do%20auth%20for%20the%20api.%26nbsp%3B%26nbsp%3BThe%20auth%20problem%20of%20Functions%20seems%20to%20be%20a%20fair%20bit%20more%20complicated%2C%20even%20with%20the%20api%20management%20included%2C%20as%20the%20functions%20seem%20to%20be%20%22accessible%22%20by%20just%20going%20to%20them%20directly%20circumventing%20the%20management.%3CBR%20%2F%3E%3CBR%20%2F%3EDoes%20this%20make%20sense%20for%20some%20pretty%20small%20almost%20%22toy%22%20applications%20for%20now%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-809722%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20API%20Management%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFunctions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EStorage%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Highlighted
Contributor

Trying to wrap my head around the "best" way to authenticate some internal tooling for our organization that integrates nicely with all the Microsoft 365 resources.  I'd like to be able to transparently utilize our existing Azure AD to authenticate these client side interfaces (teams apps, sharepoint web parts, generic web apps/desktop apps, etc) when they call back-end web APIs that will exist.

 

I'm trying to stay fairly low cost, as these are going to mostly be tiny apps e.g. some mild automations and information surfacing.  Right now I am looking at using Azure Functions + a storage account using the Tables storage API + API management to do auth for the api.  The auth problem of Functions seems to be a fair bit more complicated, even with the api management included, as the functions seem to be "accessible" by just going to them directly circumventing the management.

Does this make sense for some pretty small almost "toy" applications for now?  

0 Replies