Azure API Management Changelog https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/feed.xml Follow this feed to keep up with Azure API Management service releases. Tue, 16 Apr 2019 04:43:53 GMT en-US hourly 1 Changelog has moved. Please subscribe to the new feed. https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/changelog-has-moved-please-subscribe-to-the-new-feed Fri, 04 Dec 2015 11:17:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/12/04/changelog-has-moved-please-subscribe-to-the-new-feed/ We moved Azure API Management changelog to https://aka.ms/apimdocs. Please subscribe to the new updates feed. Thank you!

]]> June 26, 2015 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/june-26-2015 Fri, 26 Jun 2015 14:59:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/06/26/june-26-2015/ Improved
  • Validate JWT Policy. We added match attribute to the claim element to enable a degree of control over how claims in the policy are matched against the ones in the JWT
  • Proxy. In the proxy, we now strip Server header from responses
  • Developer Portal. We now hide 'Sign In' and 'Sign Up' menu items on the portal when no identity providers are selected
  • Developer Portal. We made a few changes to further improve usability of the documentation and console:
    • Response headers and response body are now shown together in a single control 
    • Request URL is back
    • Request body example, when provided, is now used to populate the request body control
    • Double-clicking in text areas selects all content to simplify copying
    • Added buttons to reveal secret values in the request
]]> May 5, 2015 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/may-5-2015 Tue, 05 May 2015 13:57:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/05/05/may-5-2015/ New
  • Set body policy. Use this policy in combination with expressions to make changes to the request and response bodies, e.g. filter information based on caller identity.
  • Per subscription analytics. We enabled per subscription reporting capability in the API and Publisher portal.

Improved

  • Publisher portal - API Import. We made import errors more specific and actionable.
  • Publisher portal - API Import. Our WADL import is now more robust and forgiving of vendor extensions.
  • Developer portal - Documentation and API Console. In are better layout, HTTP verb labels, auto-complete for common headers names, tabbed code sample gallery, and more!  
  • Validate JWT policy. Now you can configure a custom status code and message to return on token validation failure.

Fixed

  • Proxy. We heard comments about us not including a www-authenticate header in responses to requests lacking a subscription key. We do now.
]]> Apr 10, 2015 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/apr-10-2015 Wed, 08 Apr 2015 15:12:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/04/08/apr-10-2015/ New
  • Policy expressions. We now support C#-based expressions in policies. Expressions can be used as values in policy attributes and elements. Combined with the brand new control flow and set variable policies, expressions greatly increase the power and flexibility of the policy engine.
  • Control flow policy. Think of it as a switch or if-then-else construct in a programming language. Use it to conditionally apply policies based on the outcome of evaluation of logical expressions referencing request and/or response information.
  • Set variable policy. Use this policy to store a computed value for later re-use within the scope of a single request.
  • Set backend service policy. Use it with expressions to override an API's default backend URL and dynamically route requests based on the information in the request.
  • Self-signed backend certificates. By popular demand, you can now allow self-signed certificated for specific backend host names. This feature is available via API only at the moment.

Improved

  • Publisher portal - service name. Service name is now prominently featured on the Publisher portal. This should make it easier for the folks managing multiple API Management tenants to keep track of where they are.
  • Publisher portal - full screen policy editor. To make policy authoring easier we added full screen mode to the policy editor.
  • API Import. We recently introduced the ability to update an API via import as an API only feature. Now you can perform the same task in the Publisher portal.
  • Caching policy. We added an optional attribute allow-private-response-caching to the cache-lookup policy. Set it to true to turn on caching of requests containing Authorization header.

Fixed

  • Swagger 2.0 import. We dispatched the bug affecting a few customers trying to import Swagger 2.0 documents with missing optional parameters objects.
  • WADL import. We now correctly import request body representations when they are provided.
]]> Mar 12, 2015 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/mar-12-2015 Thu, 05 Mar 2015 11:53:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/03/05/mar-12-2015/ New
  • Public products. Now you can make a product public by clearing the require subscriptions checkbox. As a result, subscription key won't be needed to call the APIs included in the product.
  • Robots.txt file. You can now provide instructions to robots crawling your Developer portal by entering robots file content on the Developer portal settings page.

Improved

  • API import. We added the ability to update APIs via import. This feature is available via API only at the moment.
  • Management API. We added ability to filter entity collections on one or more entity properties. See GET /apis documentation for an example.
  • Cross domain policy. We made cross-domain policy a lot more flexible by allowing you to specify granular cross domain access rules using Adobe's Cross Domain Policy File format.
  • JWT validation policy. We simplified validate-JWT policy snippet and added first-class support for tokens issued by Azure Active Directory and Mobile Services.
  • Azure Active Directory groups support. Premium tier customers who use Azure Active Directory as an identity provider for the Developer portal can now assign product visibility directly to groups within Azure Active Directory.
  • Developer console. We improved header entry on the developer console.
]]> Jan 30, 2015 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/jan-30-2015 Thu, 29 Jan 2015 11:17:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/01/29/jan-30-2015/ New
  • Premium tier. We added a Preview of the new, high-end tier. Each Premium tier unit includes five times larger quotas than a Standard unit and can handle a substantially higher request throughput. On top of that Premium tier offers advanced features such as Azure Active Directory integration, Azure VPN support, and multi-region deployment.
  • Multi-region deployment. Bring your APIs closer to your customers by geo-distributing API management across multiple Azure datacenters and scale them based regional demand.
  • Azure Active Directory support. Enable your employees and partners to sign in to your API Management service using their corporate credentials.
  • Azure VPN support. Securely connect your API Management service to your backend web services located on-premises or in Azure and inaccessible to the public Internet.
  • JWT validation policy.  You can use this policy to ensure that a JWT extracted from a request header or query parameter is valid.
  • US Central and US East 2. We added two additional US regions for a total of 15 supported Azure regions.
  • Optional local accounts and admin only access. Publishers can now disable local accounts and allow users to sign in only with selected Internet or corporate identities. Publishers also now have the option of disabling Developer portal sign in altogether, effectively locking down access to the portal to the users coming from the Azure Management portal.

Improved

  • Product un-publishing experience. When a product is un-published, users with active subscriptions to it will continue to have access to the product and its APIs until their subscriptions expire or get cancelled.
  • Product pages. On the product pages on the Developer portal we now list APIs included in the product.
  • User subscription management. Publishers now can see and manage user keys and subscriptions in the Publisher portal.
]]> Jan 15, 2014 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/jan-15-2014 Thu, 15 Jan 2015 12:49:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2015/01/15/jan-15-2014/ New

Improved

  • Add API dialog box. Now you can save a few clicks by adding new API to one or more products at the moment of its creation.
]]> Dec 17, 2014 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/dec-17-2014 Wed, 17 Dec 2014 11:24:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2014/12/17/dec-17-2014/ New
  • Australia regions. In response to popular demand API Management can be now provisioned in both of Australia regions. This brings the number of regions where API Management is available to lucky 13.
  • Developer portal blog. Now you can create one or more blogs and make them available on the Developer portal. To start using the feature click on Blog item in the Publisher portal left navigation menu.
  • Must revalidate caching setting. We added a "must-revalidate" attribute to the "cache-lookup" policy. When downstream caching is enabled, use it to turn on or off "must-revalidate" cache control directive in proxy responses.
  • "Products" tab on the API page. You can now view and manage the list of products the API belongs on the API page in the Publisher portal.

Improved

  • Proxy performance on larger responses. We significantly improved proxy performance on responses with sizes over a few kilobytes.
  • Code samples. We reviewed and updated code samples on the Developer portal.
]]> Nov 21, 2014 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/nov-21-2014 Fri, 21 Nov 2014 13:44:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2014/11/21/nov-21-2014/ New
  • Subscription key parameter renaming. By default we expect subscription key to be provided as a value of ocp-apim-subscription-key request header or subscription-key URL query parameter.  We added the ability to customize the names of these parameters. You can now rename either one or both of them. At the moment, this feature is available via API only.
  • Compressed response handling. We now preserve "compression state" of the responses we receive from backend services. 
  • Compressed response caching. Cache policy is now compression aware and separately stores compressed and uncompressed responses.
  • Google Analytics support. Now you can enable Google Analytics on your Developer portal by going to the Settings page on the Publisher portal and clicking the "Enable Google Analytics" checkbox.

Improved

  • Multiple subscriptions per product per developer. We optimized subscription flow a little and enabled subscription name editing.
  • My Profile area on the Developer portal. It looks better and is more usable than before.

Fixed

  • Analytics graphs not populating on page load. We fixed a regression causing graphs not to populate on page load on the Dashboard.
]]> Nov 11, 2014 https://docs.microsoft.com/archive/blogs/azureapimgmt-changelog/nov-11-2014 Tue, 11 Nov 2014 14:19:00 GMT https://blogs.msdn.microsoft.com/azureapimgmt-changelog/2014/11/11/nov-11-2014/ New
  • Root APIs. We made API suffix optional and you can now publish APIs at the root of your Azure API Management service domain. This feature is available through both Publisher portal and API.
  • HTTPS and/or HTTP. We used to only expose API endpoints over secure HTTP. Now we allow you to configure either HTTPS or HTTP or both for each of your APIs. This feature is available through both Publisher portal and API.
  • Multiple subscriptions per product per developer. Users now are able to subscribe to the same API product multiple times. Publisher can set a limit on the number of same developer subscriptions for each of the products. This feature is available through both Publisher portal and API.
  • Azure regions. Azure API Management is now available in the following newly added regions: South Central US, Southeast Asia, Japan East, Japan West, Brazil South.

Improved

  • Delegation. Close account, reset password, and change profile actions are now being delegated as well.

Fixed

  • Cache policy. We now properly set max-age attribute and Expires and Pragma header values.
  • API and operation matching. We now properly interpret double slashes in the request URL as empty path segments per RFC3986.
]]>