We’re excited to introduce SCIM Provisioning to absentify! This new feature provides an alternative to our Graph Sync for organizations that prefer more granular control over the user and group data shared with absentify.

Why Choose SCIM Provisioning?

SCIM Provisioning allows you to automate user and group management in absentify by directly connecting to your Identity Provider. It’s perfect for organizations that don’t want to sync all their groups via Graph Sync and instead prefer to define exactly which data is shared with absentify.

Key Benefits

• Granular control
• Automation
• Flexibility
• Enhanced security
• Time-saving

How to Get Started

• Generate a connection token
• Configure the token
• Begin syncing only the user and group data you need—automatically.

Available Now!

• Plan
• Setup time

Take control of your absence management with SCIM Provisioning and streamline your workflows today.

👉 Learn more and get started here: Click here

We have fantastic news to share regarding privacy and compliance at absentify!

• UK GDPR Compliance:
• Updated Data Processing Agreement (DPA):
• Optimized Feedback Tool:

📄 Find all the details here: absentify Privacy

We remain committed to keeping your data safe and compliant! 🚀

Developers and power users: You can now connect your AI assistant directly to absentify. Our new MCP Server (Model Context Protocol) gives tools like Claude, ChatGPT, Cursor, or Windsurf access to the complete absentify documentation and API specification. What does this mean for you?

• Accurate code generation: Your AI assistant knows all API endpoints, parameters, and data types. No more guessing, no more copy-pasting from docs – just describe what you need and get working code.
• Instant answers: Ask your AI assistant "How do I set up approval workflows?" or "What webhook events are available?" and get precise answers based on our official documentation.
• Faster integrations: Whether you're building Power Automate flows, processing webhooks, or developing a custom integration – your AI assistant helps with the right code and the right settings.

Example prompts you can try:

• "Generate Python code that fetches all pending absence requests"
• "Create a webhook handler for approved requests"
• "How do I sync absences with our Outlook calendar?"

How it works: Simply add our MCP Server (https://absentify.com/docs/mcp) to your AI tool. Setup takes less than 2 minutes. → View setup guide

You can now create recurring absence requests in absentify. This makes it easy to set up repeating absences in just a few clicks — no need to add them manually every time. The feature is available in the Essentials plan and the Plus plan. Whether you work from home every Monday, attend vocational school every two weeks, or have any other regular schedule, recurring absences keep your planning clean, consistent, and fully visible in your team calendar. Learn how to create a recurring absence request in our documentation:$ https://absentify.com/docs/en/roles/employee/create_an_absence_request#create-a-recurring-absence-request$  Enjoy the new workflow — and as always, we’d love your feedback!

Due to a system update, Teams notifications need to be reactivated. Please open the absentify bot in Teams and send the message "activate" to reconnect.

Over the past 24 hours, absentify was unfortunately unavailable for about 20 hours. This is the longest downtime we have ever experienced, and we want to sincerely apologize for the inconvenience this caused.

Our team worked through the entire night to bring the service back online as quickly as possible. Below, we want to be transparent about what happened and how we will ensure that something like this does not happen again.

What happened?

Last night, we made a (seemingly) small update to our Azure infrastructure configuration — an update we had, of course, thoroughly tested in our staging environment beforehand. However, after rolling it out to production, unexpected issues occurred: our service was no longer able to start correctly, and reverting the original settings was no longer possible.

At the same time, the Azure region North Europe did not have enough available resources to redeploy our services. We were forced to switch to other regions, which introduced new technical challenges and delays.

In the end, we had to rebuild large parts of our network infrastructure and architecture from scratch. This process took a significant amount of time and included several unexpected difficulties along the way.

During the day, Microsoft Azure was additionally dealing with DDoS-related issues, which temporarily prevented us from deploying new resources. Once that situation was resolved, we encountered another obstacle: our build process relies on certain assets that are retrieved via Cloudflare — and Cloudflare itself experienced outages today, which disrupted our builds even further.

In short: several external factors came together at the same time, creating a chain reaction that none of our regular procedures could have anticipated.

Why this situation was entirely new for us

• We are ISO-certified and perform quarterly restore tests to ensure we can reliably recover our systems.
• However, we have never before experienced a scenario where we could neither access Azure resources nor provision new ones.
• Throughout the entire incident, we worked closely with Microsoft. Their support was excellent, but the combination of Azure resource shortages, DDoS activity, and Cloudflare outages still resulted in a long recovery time.

Current status

• absentify is fully online again and all core functionality should be working as expected.
• If you continue to experience any issues, please notify us at support@absentify.com.
• We are closely monitoring all systems to ensure stability.

How we will prevent this in the future

A downtime of this length is unacceptable to us. In the coming days, we will:

• review and redesign our infrastructure and deployment strategy,
• introduce additional redundancies for critical components,
• expand our disaster recovery planning to include rare scenarios such as Azure region shortages or Cloudflare outages,
• and put safeguards in place to ensure a single configuration update cannot trigger a cascading failure.

Our goal is clear: learn everything we can from this incident and significantly increase our resilience so that an outage of this scale does not happen again.

We are truly sorry for the inconvenience caused and greatly appreciate your patience and trust.

Your absentify Team

We're excited to announce that our feedback portal will soon be fully integrated into absentify, making it easier than ever for you to share your thoughts and ideas. With this update, you'll be automatically logged into the feedback portal when you're signed into absentify.

As part of this improvement, we'll migrate our feedback data to the European data center and onboard frill.co as a sub-processor to ensure a smooth and secure experience.

What does this mean for you?

• Effortless access
• Data security
• Enhanced experience

When is this happening?

This change will take place in four weeks.

We can't wait to share this improved feedback experience with you! Stay tuned for more updates and let us know if you have any questions.

We’ve refined the representative-field logic in absence requests to improve flexibility and transparency.

What’s new

• Administrators can configure a leave type with a “Representative requirement” setting of Required, Optional, or Not required.
• With this update, the representative dropdown is shown whenever the leave type is set to Optional or Required, even if few or no representatives are currently defined.
• In Optional mode, selecting a representative is completely optional — employees can submit a leave request without choosing one.

How it works

• In the Leave Type settings → Representative requirement:
• Representatives are managed in each employee’s profile (Settings → Users → Representative tab).

Why it matters

• Employees always see the option to assign a representative when the leave type allows it, but are no longer forced to pick one when it isn’t needed or helpful.
• HR admins retain control to require a representative when necessary, while leaving the door open for more flexible workflows.

👉 For full setup instructions, see the “Representative requirement” section under Leave Type settings in our documentation.

We're excited to introduce a new workspace management feature that helps Microsoft 365 organizations maintain a single, unified absentify workspace for all employees.

The problem we're solving

Many of our customers have repeatedly experienced the same issue: employees from the same organization who haven't received an invitation to the existing workspace simply created their own companies in absentify. This led to:

• Confusion within companies: Multiple workspaces for the same organization
• Duplicate data: Employees spread across different workspaces
• Support requests: Both from companies and from us
• Inconsistent absence management: Different policies and settings

The solution: "Prevent workspace creation for same tenant"

This new setting gives you control over whether users with the same Microsoft tenant ID can create their own workspaces.

How it works

When enabled:

• Employees from your Microsoft 365 organization must be invited to your existing workspace
• They won't see the option to create a new workspace during sign-in
• Perfect for organizations that want to ensure all employees join a single shared workspace
• Eliminates accidental workspace duplication within your organization

When disabled:

• Users can still access app.absentify.com and choose to either join an existing workspace or create a new one under the same tenant

When should you enable this feature?

Recommendation: Enable this setting when:

• You want all employees to use the same workspace
• You've already experienced problems with multiple workspaces
• You want centralized absence management for your entire organization

Example:Imagine you have 50 employees in your company. Without this setting, it could happen that 5 different department managers create their own workspaces because they didn't know one already existed. This leads to 5 different absence policies, 5 different vacation quotas, and 5 different approval processes.

Setup

1. Go to Settings → Organization → General
2. Find the "Prevent workspace creation for same tenant" toggle
3. Enable the setting

Important: If other workspaces already exist within your organization, you'll need to resolve these conflicts before enabling this setting.

Learn more

For detailed information about this feature and other workspace settings, visit our documentation.

This feature is now available for all absentify workspaces. Let us know what you think!

We’ve just released an update to make department management even more flexible!

Admins can now submit leave requests on behalf of employees even if the request exceeds the department’s configured ‘Maximum Absent’ limit.

This means you can handle exceptional situations—like urgent leave needs—without having to change department settings first.

Why you’ll love it:

• Keeps your ‘Maximum Absent’ rules in place for normal operations.
• Gives admins the power to make exceptions when necessary.
• Saves time by avoiding extra configuration steps.

🔗 Learn more in our documentation: Maximum Absent Settings

To try it out, simply create a leave request as an admin for any employee—absentify will now allow you to override the limit when needed.