Feature: Add Support for Azure EntraID for SMTP

Abierto
#15,482 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript

Línea de trabajo

Start by locating Appwrite Messaging’s SMTP provider configuration and mail delivery entry points, then read how existing SMTP authentication and provider credentials are handled. The issue does not name files or tests, so trace those paths before estimating the change. Done means administrators can configure Microsoft Entra ID OAuth 2.0 client credentials for Microsoft 365 SMTP and send transactional email without basic SMTP authentication.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

product / messaging
🔖 Enhancement description

Support Microsoft Entra ID (Azure AD) OAuth 2.0 authentication for SMTP email providers, allowing Appwrite Messaging to send email through Microsoft 365 without requiring basic username/password SMTP authentication.

This would enable administrators to configure Microsoft 365 SMTP using modern authentication methods, including OAuth 2.0 client credentials and application registrations, in line with Microsoft's recommended security practices

🎤 Pitch

Many organisations are moving away from basic SMTP authentication and adopting Microsoft Entra ID (Azure AD) and OAuth 2.0 as their standard approach for Microsoft 365 email services. Microsoft now recommend this as best practice.

Without Entra ID support, Appwrite users in enterprise, education, and public-sector environments may be unable to use Microsoft 365 as an SMTP provider due to security policies that prohibit password-based authentication.

Adding Entra ID SMTP support would enable secure integration with Microsoft 365 for common use cases such as account verification, password resets, and transactional emails, while aligning Appwrite with modern security best practices and reducing reliance on stored credentials.

👀 Have you spent some time to check if this issue has been raised before?
  • I checked and didn't find similar issue
🏢 Have you read the Code of Conduct?
Lenguaje dominante
TypeScript
Estrellas
57.9k
Forks
5.8k
Merge medio
16 h 1 min
PR fusionados (30 d)
768

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de appwrite/appwrite

Todos los issues de appwrite/appwrite

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.