You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory/fundamentals/whats-new-archive.md
-200Lines changed: 0 additions & 200 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8337,203 +8337,3 @@ By setting up federation with Google in your organization, you can let invited G
8337
8337
This is an opt-in public preview. For more information about Google federation, see [Add Google as an identity provider for B2B guest users](../external-identities/google-federation.md).
8338
8338
8339
8339
---
8340
-
8341
-
## July 2018
8342
-
8343
-
### Improvements to Azure Active Directory email notifications
Azure Active Directory (Azure AD) emails now feature an updated design, as well as changes to the sender email address and sender display name, when sent from the following services:
For an example of some of the new e-mail designs and more information, see [Email notifications in Azure AD PIM](../privileged-identity-management/pim-email-notifications.md).
8364
-
8365
-
---
8366
-
8367
-
### Azure AD Activity Logs are now available through Azure Monitor
8368
-
8369
-
**Type:** New feature
8370
-
**Service category:** Reporting
8371
-
**Product capability:** Monitoring & Reporting
8372
-
8373
-
The Azure AD Activity Logs are now available in public preview for the Azure Monitor (Azure's platform-wide monitoring service). Azure Monitor offers you long-term retention and seamless integration, in addition to these improvements:
8374
-
8375
-
- Long-term retention by routing your log files to your own Azure storage account.
8376
-
8377
-
- Seamless SIEM integration, without requiring you to write or maintain custom scripts.
8378
-
8379
-
- Seamless integration with your own custom solutions, analytics tools, or incident management solutions.
8380
-
8381
-
For more information about these new capabilities, see our blog [Azure AD activity logs in Azure Monitor diagnostics is now in public preview](https://cloudblogs.microsoft.com/enterprisemobility/2018/07/26/azure-ad-activity-logs-in-azure-monitor-diagnostics-now-in-public-preview/) and our documentation, [Azure Active Directory activity logs in Azure Monitor (preview)](../reports-monitoring/concept-activity-logs-azure-monitor.md).
8382
-
8383
-
---
8384
-
8385
-
### Conditional Access information added to the Azure AD sign-ins report
This update lets you see which policies are evaluated when a user signs in along with the policy outcome. In addition, the report now includes the type of client app used by the user, so you can identify legacy protocol traffic. Report entries can also now be searched for a correlation ID, which can be found in the user-facing error message and can be used to identify and troubleshoot the matching sign-in request.
8392
-
8393
-
---
8394
-
8395
-
### View legacy authentications through Sign-ins activity logs
8396
-
8397
-
**Type:** New feature
8398
-
**Service category:** Reporting
8399
-
**Product capability:** Monitoring & Reporting
8400
-
8401
-
With the introduction of the **Client App** field in the Sign-in activity logs, customers can now see users that are using legacy authentications. Customers will be able to access this information using the Sign-ins Microsoft Graph API or through the Sign-in activity logs in Azure portal where you can use the **Client App** control to filter on legacy authentications. Check out the documentation for more details.
8402
-
8403
-
---
8404
-
8405
-
### New Federated Apps available in Azure AD app gallery - July 2018
8406
-
8407
-
**Type:** New feature
8408
-
**Service category:** Enterprise Apps
8409
-
**Product capability:** 3rd Party Integration
8410
-
8411
-
In July 2018, we've added these 16 new apps with Federation support to the app gallery:
For more information about the apps, see [SaaS application integration with Azure Active Directory](../saas-apps/tutorial-list.md). For more information about listing your application in the Azure AD app gallery, see [List your application in the Azure Active Directory application gallery](../manage-apps/v2-howto-app-gallery-listing.md).
8416
-
8417
-
---
8418
-
8419
-
### New user provisioning SaaS app integrations - July 2018
8420
-
8421
-
**Type:** New feature
8422
-
**Service category:** App Provisioning
8423
-
**Product capability:** 3rd Party Integration
8424
-
8425
-
Azure AD allows you to automate the creation, maintenance, and removal of user identities in SaaS applications such as Dropbox, Salesforce, ServiceNow, and more. For July 2018, we have added user provisioning support for the following applications in the Azure AD app gallery:
For a list of all applications that support user provisioning in the Azure AD gallery, see [SaaS application integration with Azure Active Directory](../saas-apps/tutorial-list.md).
8432
-
8433
-
---
8434
-
8435
-
### Connect Health for Sync - An easier way to fix orphaned and duplicate attribute sync errors
8436
-
8437
-
**Type:** New feature
8438
-
**Service category:** AD Connect
8439
-
**Product capability:** Monitoring & Reporting
8440
-
8441
-
Azure AD Connect Health introduces self-service remediation to help you highlight and fix sync errors. This feature troubleshoots duplicated attribute sync errors and fixes objects that are orphaned from Azure AD. This diagnosis has the following benefits:
8442
-
8443
-
- Narrows down duplicated attribute sync errors, providing specific fixes
8444
-
8445
-
- Applies a fix for dedicated Azure AD scenarios, resolving errors in a single step
8446
-
8447
-
- No upgrade or configuration is required to turn on and use this feature
8448
-
8449
-
For more information, see [Diagnose and remediate duplicated attribute sync errors](../hybrid/how-to-connect-health-diagnose-sync-errors.md)
8450
-
8451
-
---
8452
-
8453
-
### Visual updates to the Azure AD and MSA sign-in experiences
8454
-
8455
-
**Type:** Changed feature
8456
-
**Service category:** Azure AD
8457
-
**Product capability:** User Authentication
8458
-
8459
-
We've updated the UI for Microsoft's online services sign-in experience, such as for Office 365 and Azure. This change makes the screens less cluttered and more straightforward. For more information about this change, see the [Upcoming improvements to the Azure AD sign-in experience](https://cloudblogs.microsoft.com/enterprisemobility/2018/04/04/upcoming-improvements-to-the-azure-ad-sign-in-experience/) blog.
- General Availability of the Ping-Federate integration
8474
-
8475
-
- Updates to the latest SQL 2012 client
8476
-
8477
-
For more information about this update, see [Azure AD Connect: Version release history](../hybrid/reference-connect-version-history.md)
8478
-
8479
-
---
8480
-
8481
-
### Updates to the terms of use end-user UI
8482
-
8483
-
**Type:** Changed feature
8484
-
**Service category:** Terms of use
8485
-
**Product capability:** Governance
8486
-
8487
-
We're updating the acceptance string in the TOU end-user UI.
8488
-
8489
-
**Current text.** In order to access [tenantName] resources, you must accept the terms of use.<br>**New text.** In order to access [tenantName] resource, you must read the terms of use.
8490
-
8491
-
**Current text:** Choosing to accept means that you agree to all of the above terms of use.<br>**New text:** Please select Accept to confirm that you have read and understood the terms of use.
8492
-
8493
-
---
8494
-
8495
-
### Pass-through Authentication supports legacy protocols and applications
8496
-
8497
-
**Type:** Changed feature
8498
-
**Service category:** Authentications (Logins)
8499
-
**Product capability:** User Authentication
8500
-
8501
-
Pass-through Authentication now supports legacy protocols and apps. The following limitations are now fully supported:
8502
-
8503
-
- User sign-ins to legacy Office client applications, Office 2010 and Office 2013, without requiring modern authentication.
8504
-
8505
-
- Access to calendar sharing and free/busy information in Exchange hybrid environments on Office 2010 only.
8506
-
8507
-
- User sign-ins to Skype for Business client applications without requiring modern authentication.
8508
-
8509
-
- User sign-ins to PowerShell version 1.0.
8510
-
8511
-
- The Apple Device Enrollment Program (Apple DEP), using the iOS Setup Assistant.
8512
-
8513
-
---
8514
-
8515
-
### Converged security info management for self-service password reset and MultiFactor Authentication
8516
-
8517
-
**Type:** New feature
8518
-
**Service category:** SSPR
8519
-
**Product capability:** User Authentication
8520
-
8521
-
This new feature lets users manage their security info (for example, phone number, email address, mobile app, and so on) for self-service password reset (SSPR) and multifactor authentication (MFA) in a single experience. Users will no longer have to register the same security info for SSPR and multifactor authentication (MFA) in two different experiences. This new experience also applies to users who have either SSPR or multifactor authentication (MFA).
8522
-
8523
-
If an organization isn't enforcing multifactor authentication (MFA) or SSPR registration, users can register their security info through the **My Apps** portal. From there, users can register any methods enabled for multifactor authentication (MFA) or SSPR.
8524
-
8525
-
This is an opt-in public preview. Admins can turn on the new experience (if desired) for a selected group of users or all users in a tenant.
8526
-
8527
-
---
8528
-
8529
-
### Use the Microsoft Authenticator app to verify your identity when you reset your password
8530
-
8531
-
**Type:** Changed feature
8532
-
**Service category:** SSPR
8533
-
**Product capability:** User Authentication
8534
-
8535
-
This feature lets non-admins verify their identity while resetting a password using a notification or code from Microsoft Authenticator (or any other authenticator app). After admins turn on this self-service password reset method, users who have registered a mobile app through aka.ms/mfasetup or aka.ms/setupsecurityinfo can use their mobile app as a verification method while resetting their password.
8536
-
8537
-
Mobile app notification can only be turned on as part of a policy that requires two methods to reset your password.
0 commit comments