Skip to content

Commit c1345b6

Browse files
authored
Merge pull request #49606 from eross-msft/aug-whats-new
What's New content for August
2 parents e9b0a9c + 69d7423 commit c1345b6

File tree

1 file changed

+108
-3
lines changed

1 file changed

+108
-3
lines changed

articles/active-directory/fundamentals/whats-new.md

Lines changed: 108 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,7 @@ Azure AD receives improvements on an ongoing basis. To stay up-to-date with the
3232
This page is updated monthly, so revisit it regularly.
3333

3434
---
35-
36-
## July 2018
35+
## August 2018
3736

3837
### Changes to Azure Active Directory IP address ranges
3938

@@ -49,10 +48,116 @@ Network traffic is moving to these new ranges over the next two months. To conti
4948

5049
- 40.126.0.0/18
5150

52-
We strongly recommend not removing the old IP Address ranges until all of your network traffic has moved to the new ranges. For updates about the move and to learn when you can remove the old ranges, see [Office 365 URLs and IP address ranges](https://support.office.com/en-us/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2).
51+
We strongly recommend not removing the old IP Address ranges until all of your network traffic has moved to the new ranges. For updates about the move and to learn when you can remove the old ranges, see [Office 365 URLs and IP address ranges](https://support.office.com/article/Office-365-URLs-and-IP-address-ranges-8548a211-3fe7-47cb-abb1-355ea5aa88a2).
52+
53+
---
54+
55+
### Change notice: Authorization codes will no longer be available for reuse
56+
57+
**Type:** Plan for change
58+
**Service category:** Authentications (Logins)
59+
**Product capability:** User Authentication
60+
61+
Starting on October 10, 2018, Azure AD will stop accepting previously-used authentication codes for new apps. Any app created before October 10, 2018 will still be able to reuse authentication codes. This security change helps to bring Azure AD in line with the OAuth specification and will be enforced on both the v1 and v2 endpoints.
62+
63+
If your app reuses authorization codes to get tokens for multiple resources, we recommend that you use the code to get a refresh token, and then use that refresh token to acquire additional tokens for other resources. Authorization codes can only be used once, but refresh tokens can be used multiple times across multiple resources. Any new app that attempts to reuse an authentication code during the OAuth code flow will get an invalid_grant error, revoking the previous refresh token that was acquired using that duplicate code.
64+
65+
For more information about refresh tokens, see [Refreshing the access tokens](https://docs.microsoft.com/azure/active-directory/develop/v1-protocols-oauth-code#refreshing-the-access-tokens).
66+
67+
---
68+
69+
### Converged security info management for self-service password (SSPR) and Multi-Factor Authentication (MFA)
70+
71+
**Type:** New feature
72+
**Service category:** SSPR
73+
**Product capability:** User Authentication
74+
75+
This new feature helps people manage their security info (such as, phone number, mobile app, and so on) for SSPR and MFA in a single location and experience; as compared to previously, where it was done in two different locations.
76+
77+
This converged experience also works for people using either SSPR or MFA. Additionally, if your organization doesn't enforce MFA or SSPR registration, people can still register any MFA or SSPR security info methods allowed by your organization from the My Apps portal.
5378

79+
This is an opt-in public preview. Administrators can turn on the new experience (if desired) for a selected group or for all users in a tenant. For more information about the converged experience, see the [Converged experience blog](https://cloudblogs.microsoft.com/enterprisemobility/2018/08/06/mfa-and-sspr-updates-now-in-public-preview/)
80+
81+
---
82+
83+
### New HTTP-Only cookies setting in Azure AD Application proxy apps
84+
85+
**Type:** New feature
86+
**Service category:** App Proxy
87+
**Product capability:** Access Control
88+
89+
There's a new setting called, **HTTP-Only Cookies** in your Application Proxy apps. This setting helps provide extra security by including the HTTPOnly flag in the HTTP response header for both Application Proxy access and session cookies, stopping access to the cookie from a client-side script and further preventing actions like copying or modifying the cookie. Although this flag hasn't been used previously, your cookies have always been encrypted and transmitted using a SSL connection to help protect against improper modifications.
90+
91+
This setting isn't compatible with apps using ActiveX controls, such as Remote Desktop. If you're in this situation, we recommend that you turn this setting off.
92+
93+
For more information about the HTTP-Only Cookies setting, see [Publish applications using Azure AD Application Proxy](https://docs.microsoft.com/azure/active-directory/manage-apps/application-proxy-publish-azure-portal).
94+
95+
---
96+
97+
### Privileged Identity Management (PIM) for Azure resources supports Management Group resource types
98+
99+
**Type:** New feature
100+
**Service category:** Privileged Identity Management
101+
**Product capability:** Privileged Identity Management
102+
103+
Just-In-Time activation and assignment settings can now be applied to Management Group resource types, just like you already do for Subscriptions, Resource Groups, and Resources (such as VMs, App Services, and more). In addition, anyone with a role that provides administrator access for a Management Group can discover and manage that resource in PIM.
104+
105+
For more information about PIM and Azure resources, see [Discover and manage Azure resources by using Privileged Identity Management](https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-resource-roles-discover-resources)
106+
54107
---
55108

109+
### Application access (preview) provides faster access to the Azure AD portal
110+
111+
**Type:** New feature
112+
**Service category:** Privileged Identity Management
113+
**Product capability:** Privileged Identity Management
114+
115+
Today, when activating a role using PIM, it can take over 10 minutes for the permissions to take effect. If you choose to use Application access, which is currently in public preview, administrators can access the Azure AD portal as soon as the activation request completes.
116+
117+
Currently, Application access only supports the Azure AD portal experience and Azure resources. For more information about PIM and Application access, see [What is Azure AD Privileged Identity Management?](https://docs.microsoft.com/azure/active-directory/privileged-identity-management/pim-configure)
118+
119+
---
120+
121+
### New Federated Apps available in Azure AD app gallery - August 2018
122+
123+
**Type:** New feature
124+
**Service category:** Enterprise Apps
125+
**Product capability:** 3rd Party Integration
126+
127+
In August 2018, we've added these 16 new apps with Federation support to the app gallery:
128+
129+
[Hornbill](https://docs.microsoft.com/azure/active-directory/saas-apps/hornbill-tutorial), [Bridgeline Unbound](https://docs.microsoft.com/azure/active-directory/saas-apps/bridgelineunbound-tutorial), [Sauce Labs - Mobile and Web Testing](https://docs.microsoft.com/azure/active-directory/saas-apps/saucelabs-mobileandwebtesting-tutorial), [Meta Networks Connector](https://docs.microsoft.com/azure/active-directory/saas-apps/metanetworksconnector-tutorial), [Way We Do](https://docs.microsoft.com/azure/active-directory/saas-apps/waywedo-tutorial), [Spotinst](https://docs.microsoft.com/azure/active-directory/saas-apps/spotinst-tutorial), [ProMaster (by Inlogik)](https://docs.microsoft.com/azure/active-directory/saas-apps/promaster-tutorial), SchoolBooking, [4me](https://docs.microsoft.com/azure/active-directory/saas-apps/4me-tutorial), [Dossier](https://docs.microsoft.com/azure/active-directory/saas-apps/DOSSIER-tutorial), [N2F - Expense reports](https://docs.microsoft.com/azure/active-directory/saas-apps/n2f-expensereports-tutorial), [Comm100 Live Chat](https://docs.microsoft.com/azure/active-directory/saas-apps/comm100livechat-tutorial), [SafeConnect](https://docs.microsoft.com/azure/active-directory/saas-apps/safeconnect-tutorial), [ZenQMS](https://docs.microsoft.com/azure/active-directory/saas-apps/zenqms-tutorial), [eLuminate](https://docs.microsoft.com/azure/active-directory/saas-apps/eluminate-tutorial), [Dovetale](https://docs.microsoft.com/azure/active-directory/saas-apps/dovetale-tutorial).
130+
131+
For more information about the apps, see [SaaS application integration with Azure Active Directory](https://aka.ms/appstutorial). For more information about listing your application in the Azure AD app gallery, see [List your application in the Azure Active Directory application gallery](https://aka.ms/azureadapprequest).
132+
133+
---
134+
135+
### Native Tableau support is now available in Azure AD Application Proxy
136+
137+
**Type:** Changed feature
138+
**Service category:** App Proxy
139+
**Product capability:** Access Control
140+
141+
With our update from the OpenID Connect to the OAuth 2.0 Code Grant protocol for our pre-authentication protocol, you no longer have to do any additional configuration to use Tableau with Application Proxy. This protocol change also helps Application Proxy better support more modern apps by using only HTTP redirects, which are commonly supported in JavaScript and HTML tags.
142+
143+
For more information about our native support for Tableau, see [Azure AD Application Proxy now with native Tableau support](https://blogs.technet.microsoft.com/applicationproxyblog/2018/08/14/azure-ad-application-proxy-now-with-native-tableau-support).
144+
145+
---
146+
147+
### New support to add Google as an identity provider for B2B guest users in Azure Active Directory (preview)
148+
149+
**Type:** New feature
150+
**Service category:** B2B
151+
**Product capability:** B2B/B2C
152+
153+
By setting up federation with Google in your organization, you can let invited Gmail users sign-in to your shared apps and resources using their existing Google account, without having to create a personal Microsoft Account (MSAs) or an Azure AD account.
154+
155+
This is an opt-in public preview. For more information about Google federation, see [Add Google as an identity provider for B2B guest users](https://docs.microsoft.com/en-us/azure/active-directory/b2b/google-federation).
156+
157+
---
158+
159+
## July 2018
160+
56161
### Improvements to Azure Active Directory email notifications
57162

58163
**Type:** Changed feature

0 commit comments

Comments
 (0)