SharePoint - Alternate Access Mapping (AAM)

The following is a SharePoint dictionary word of the day: Alternate Access Mapping (AAM):

Alternate Access Mapping (AAM) is one of those foundational SharePoint concepts that quietly powers a smooth user experience—yet most administrators rarely talk about it. If you manage SharePoint Online or SharePoint Server, understanding AAM helps you control how users reach your content and how SharePoint renders that content in the correct URL environment.

What Alternate Access Mapping Actually Does

At its core, Alternate Access Mapping is a system that maps multiple URLs to a single SharePoint web application. This allows SharePoint to understand where a request is coming from and how content should be served back.

Incoming vs. Outgoing Mappings

SharePoint uses two sides of AAM, each with a distinct purpose:

Incoming Mappings — These define how users access your site.

They allow multiple entry points (example: internal URL, external URL, load‑balanced URL) to reach the same content.

Outgoing Mappings — These ensure SharePoint responds with the correct URL.

This is crucial for proper rendering of links, images, navigation, and service calls.

Why AAM Matters

AAM becomes essential in scenarios such as:

1. Reverse proxy or firewall‑based publishing
2. Hybrid or split‑DNS environments
3. Multiple zones (Default, Intranet, Extranet, Internet)
4. Load‑balanced or geo‑distributed access
5. Custom vanity URLs for branding or user experience

Without proper AAM configuration, users may see broken links, mismatched URLs, or inconsistent navigation behavior.

Practical Example

Imagine your SharePoint site is accessible internally at:

https://test1.sharepoint.com

But externally, you publish it through a secure domain:

https://test.sharepoint.com

AAM allows both URLs to reach the same content while ensuring SharePoint renders pages using the correct outbound URL depending on the access zone.

Best Practices

• Always map URLs to the correct zone (Default, Intranet, Extranet, Internet).
• Use vanity URLs for user‑friendly access.
• Validate outgoing mappings after any DNS or proxy change.
• Document your AAM strategy as part of your governance model.

Key Takeaway

Alternate Access Mapping is the backbone of multi‑URL access in SharePoint. It ensures users can reach your content from different entry points while guaranteeing that SharePoint responds with the correct, expected URL every time.

SharePoint - Rules

The following is a SharePoint dictionary word of the day: Rules.

What Are Rules in SharePoint Online?

Rules in SharePoint Online are automated notifications that help you stay informed when specific changes occur in your SharePoint environment. Instead of manually checking documents, lists, pages, or sites for updates, you can create a rule that automatically sends a notification when a defined condition is met.

Once a rule is configured, SharePoint monitors the selected content for changes. When the specified criteria are satisfied, SharePoint automatically sends a notification to the appropriate users.

How Do SharePoint Online Rules Work?

A SharePoint rule typically works in three simple steps:

Create a rule – Select the SharePoint content you want to monitor and define the condition that should trigger the notification.

SharePoint monitors for changes – After the rule is enabled, SharePoint automatically watches for the specified activity.

Receive a notification – When the condition is met, SharePoint sends an automatic notification.

For example, you can create a rule to notify team members when a document is modified in a SharePoint document library. This can help users stay up to date without constantly checking the library for changes.

What Can SharePoint Rules Monitor?

Depending on your SharePoint Online configuration, rules can be used with different types of content and activities, including:

• Documents and files
• Document libraries
• SharePoint lists and list items
• Pages
• Other SharePoint content and assets

Why Use Rules in SharePoint Online?

Rules can make everyday SharePoint management easier by reducing the need for manual monitoring. They are particularly useful for teams that need timely notifications about document updates, list changes, or other important activity.

By automating these notifications, SharePoint rules can improve collaboration, help users respond to changes faster, and make it easier to keep track of frequently updated content.

Final Thoughts

SharePoint Online rules provide a simple way to automate notifications when important changes occur. Once configured, the rule works automatically in the background, helping you stay informed about updates to documents, lists, pages, and other SharePoint content.

If your team frequently checks SharePoint manually for updates, creating rules can be a useful way to save time and improve productivity.

See the official documentation on this subject:

Create a rule to automate a list or library

https://support.microsoft.com/en-us/sharepoint/lists/documents-and-library/create-a-rule-to-automate-a-list-or-library

SharePoint - After Events

The following is a SharePoint dictionary word of the day: After events.

After Events in SharePoint: The Asynchronous Power Feature You’re Probably Not Using Yet

If you work with SharePoint automation, event receivers, or custom business logic, understanding the after event model is essential. It’s one of those quiet-but-powerful features that can make your environment faster, safer, and more predictable — especially when dealing with heavy or complex operations.

What Is an “After Event” in SharePoint?

An after event is an asynchronous event that fires only after the action that raised the event has fully completed.

That means:

• The user action finishes first
• SharePoint commits the change
• Then your custom logic runs in the background
• This is different from synchronous events, which block the user until your code finishes.

Why After Events Matter

After events are the backbone of smooth, scalable SharePoint automation. They allow you to run logic without slowing down the user experience.

Here’s why they’re so valuable:

• Non-blocking performance — Users don’t wait for your code to finish.
• Reliable sequencing — The item or document is already saved before your handler runs.
• Safe for heavy operations — Perfect for long-running or resource-intensive tasks.
• Ideal for integrations — APIs, external databases, and cloud services won’t freeze the UI.

Real SharePoint Example: Why After Events Shine

Imagine a user updates a list item that triggers your automation. You want to:

• Generate a PDF
• Push data to an external CRM
• Update a dashboard
• Send notifications
• Log activity to an audit list

Doing this synchronously would slow down the save operation.

With an after event, the user sees the update complete instantly — while your automation quietly handles everything behind the scenes.

Common Use Cases for After Events

Use after events when your logic is:

• Batch-oriented
• Non-critical to immediate user action
• Dependent on the final saved state
• Triggered by workflows or automation

Avoid them when you need to validate or block an action — that’s synchronous territory.