microsoft-azure-webjobs-extensions-authentication-events-dotnet
Build Microsoft Entra Authentication Event Functions
Custom authentication extensions require precise event contracts and response actions. This skill provides focused .NET patterns for Azure Functions and Microsoft Entra events.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "microsoft-azure-webjobs-extensions-authentication-events-dotnet" from https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet.md and its manifest at https://skillstore.io/api/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
GET /skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet.md Signed manifest GET /api/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/manifest Signed lockfile GET /api/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/lockfileTest it
Using "microsoft-azure-webjobs-extensions-authentication-events-dotnet". Create a token issuance handler that adds department and employee identifier claims.
Expected outcome:
- Handler outline for the token issuance event
- Checks for a valid user identifier before lookup
- Returns only approved department and employee identifier claims
- Uses a continuation response when enrichment fails
Using "microsoft-azure-webjobs-extensions-authentication-events-dotnet". Review an attribute collection handler for production readiness.
Expected outcome:
- Validation gaps for missing and malformed attributes
- Recommended blocking and field-error responses
- Logging changes that protect personal data
- Tests for valid, invalid, missing, and provider-failure cases
Using "microsoft-azure-webjobs-extensions-authentication-events-dotnet". Plan a custom OTP delivery integration.
Expected outcome:
A delivery workflow covering provider authentication, timeout handling, protected logs, success responses, failure responses, and retry boundaries.
Security Audit
SafeAll 54 static findings are false positives caused by Markdown formatting, illustrative code, reserved example URLs, official reference links, or ordinary guidance. No executable automation, prompt injection, data exfiltration intent, or malicious system reconnaissance was found.
Risk Factors
โ๏ธ External commands (47)
๐ Network access (6)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
sickn33. (2026). microsoft-azure-webjobs-extensions-authentication-events-dotnet security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/audits/5BibTeX citation
@techreport{sickn33-sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet-2026,
author = {sickn33},
title = {microsoft-azure-webjobs-extensions-authentication-events-dotnet security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "microsoft-azure-webjobs-extensions-authentication-events-dotnet security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "sickn33"
date-released: "2026-08-04"
url: "https://skillstore.io/skills/sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet/audits/5"
identifiers:
- type: other
value: "skillstore:sickn33-microsoft-azure-webjobs-extensions-authentication-events-dotnet:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Enrich issued tokens
Design a token issuance function that retrieves trusted profile data and returns approved custom claims.
Validate sign-up attributes
Create attribute collection handlers that prefill values, reject invalid submissions, and normalize accepted data.
Plan custom OTP delivery
Structure an OTP event handler for an approved SMS, email, or push provider.
Try These Prompts
Create a .NET Azure Function for OnTokenIssuanceStart. Add department and cost center claims from trusted input. Include validation and error handling.
Build an OnAttributeCollectionSubmit handler. Validate email and display name, return field errors, and normalize accepted values.
Design token enrichment using an external profile API. Include authentication, timeouts, caching, response validation, fallback behavior, and privacy-safe logging.
Review my Entra authentication event design for security, latency, failure behavior, permissions, claims integrity, observability, and deployment readiness.
Best Practices
- Validate event payloads and external data before adding claims or modifying user attributes.
- Use managed identities, narrow permissions, strict timeouts, and explicit fallback behavior for dependencies.
- Log correlation identifiers while excluding OTP values, tokens, phone numbers, and unnecessary personal data.
Avoid
- Do not trust external profile fields or place unrestricted data into token claims.
- Do not throw unhandled exceptions that can interrupt the authentication flow.
- Do not place secrets, OTP values, access tokens, or personal identifiers in logs.